You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This expression need to be stricter to prevent matching characters within a base64 encoded string. This issue was identified in our application, where this buggyfill script was "corrupting" base64 encoded images.
I wonder if simply adding word boundary metacharacters around the expression will suffice, but as this repository does not contain any sort of automated testing tools, I cannot be sure, and I don't really have the time to manually test this change.
// originalvarviewportUnitExpression=/([+-]?[0-9.]+)(vh|vw|vmin|vmax)/g;// yoursvarviewportUnitExpression=/\b([+-]?[0-9.]+)(vh|vw|vmin|vmax)\b/g;// considering that - and + match \b anywaysvarviewportUnitExpression=/((+|-|\b)[0-9.]+)(vh|vw|vmin|vmax)\b/g;
See:
viewport-units-buggyfill/viewport-units-buggyfill.js
Line 28 in 0c5f077
This expression need to be stricter to prevent matching characters within a base64 encoded string. This issue was identified in our application, where this buggyfill script was "corrupting" base64 encoded images.
I wonder if simply adding word boundary metacharacters around the expression will suffice, but as this repository does not contain any sort of automated testing tools, I cannot be sure, and I don't really have the time to manually test this change.
Here's the change: https://gist.github.com/badsyntax/bc4423dc51b04f54ae52/revisions
The text was updated successfully, but these errors were encountered: