if all else fails you can inspect which events are linked to your elements with visual event: http://www.sprymedia.co.uk/article/visual+event This adds an overlayer to any web page and let you visually inspect the JS code that’s linked to an element (it shows you the piece of code in a pop up). this way you can easily … Read more
I suspect there’s no other solution than to rewrite the parts of Modernizr that use inline code or dynamically evaluated code (which applies to both JS and CSS). The experiences of AngularJS ngCsp might be useful here.
So the way these web inspectors work is that they use the RemoteDebug Protocol. This protocol defines the various messages and commands that are exchanged to let you ‘inspect’ your pages. One instance of the inspector can only connect to one client at a time. So assuming that you are switching to and fro web-views … Read more
https://pdf-lib.js.org/ library supports modification of existing PDF file. const pdfDoc = await PDFDocument.load(…) const pages = pdfDoc.getPages() pages[0].drawText(‘You can modify PDFs too!’) const pdfBytes = await pdfDoc.save()
You are able to get a visual performance boost by implementing will-change on elements. It is supported in recent browsers (excluding edge and no IE). The will-change CSS property hints to browsers how an element is expected to change. Browsers may set up optimizations before an element is actually changed. These kinds of optimizations can … Read more
I can’t find a suitable event for that. Yeah, there isn’t one. There are DOM Mutation Events, but they aren’t supported well cross-browser, and don’t fire for form values anyway as those aren’t reflected in attributes (except in IE due to a bug). In Mozilla only, a JavaScript watch could be set on the value … Read more
Anything that is going to change goes in State. If you’re looking at loading an existing entity and editing it, you want controlled inputs, and you want to set the values accordingly. I tend to stay away from defaultValue in most cases (outside of dropdowns) This ties back in to your previous question. If you … Read more
There are of course legit reasons to force synchronous execution of a promise in js. The most obvious is when require‘ing a file that needs to initialize using some asynchronous stuff, and optimization is not an overriding concern. Seems like the package synchronized-promise seems like it ought to do the trick. In your case (warning … Read more
When you run code in Firefox, you can often see huge drop in speed for asm.js calls, which is most probably caused either by repeated compilation (which is visible in console) or by cost of js-to-asm calls. This hypothesis is further strenghtened by Luke Wagner, implementor of asm.js: one performance fault that we already know … Read more
escape() is defined in section B.2.1.2 escape and the introduction text of Annex B says: … All of the language features and behaviours specified in this annex have one or more undesirable characteristics and in the absence of legacy usage would be removed from this specification. … For characters, whose code unit value is 0xFF … Read more