Paul Jones

This is still valid for 1.0.0d (in my setup) A workaround can be found by fixing/updating a line in the viewer-static.min.js in the snapshot to include the base path: The...

While this isn't the same issue, I have noticed that when editing the flow charting plugin, the memory allocation keeps growing and growing and I've had pages crash because of...

This issue is invalid as I suffered the same problem, but selecting one folder deeper in the zip folder fixed it. A longer-lasting fix would be updating the documentation to...

Looking at #394, this is similar issue as #401

Building on this, to get rid of the dollar sign, comma and periods, use this XPATH filter: /html/body/div[3]/div[4]/section/section/div[6]/div[2]/div[2]/div[1]/div/div/div[number(translate(text(), '$,.', '')) < 129999] This does the logic on the XPATH of:...

Afaik Chrome V2 removal has been delayed till June. Firefox will continue V2 support for the foreseeable future https://developer.chrome.com/docs/extensions/mv3/mv2-sunset/ https://www.techspot.com/news/97302-mozilla-confirms-wont-cripple-manifest-v2-ad-blockers.html

For context this applies to 1.0.0b and 1.0.0d

I'm assuming everyone is experiencing the same issue as me, where the output of draw.io is a block of unknown Base64 text. I ran my block in CyberChef Magic and...

@teguhsatria892 I noticed you forked the repository. Did you manage to fix the zoom in/out issue? Also did you manage to fix the Draw.io editing issue?

Is there a workaround for this? Also I would like to note that I encountered a similar issue, but with the module.js.map file instead: `logger=plugin.loader t=2023-03-29T17:30:16.274358585Z level=warn msg="Plugin file checksum...