4 ms·
Well, on one hand it will certainly lighten the ressources needed. On the other hand, you don’t know on what version of Chrome/Chromium you’ll land so you won’
by JeanMarcS 8y ago
Well, on one hand it will certainly lighten the ressources needed.
On the other hand, you don’t know on what version of Chrome/Chromium you’ll land so you won’t be able to use specific API for sure.
But for having developed in the end of the 90’s a web kiosk software, based on Internet Explorer (I think it was IE5 back then), software that still have last versions running (no one, including myself, would thought it’ll survive that long), I will sure have a look closer on the project if you can intercept the before navigate event (or whatever the name is with Chrome)
- johnisgood 8y ago> On the other hand, you don’t know on what version of Chrome/Chromium you’ll land so you won’t be able to use specific API for sure. Is it just me, or the API changes and breaks way too often? I recently wanted to make an extension and I Google'd here and there, and all the code posted just a few months ago is now obsolete. It is crazy!
- giancarlostoro 8y agoI think WebExtensions might be to blame for that, but without more information as to what wasn't working I couldn't say.
- Scarbutt 8y agoYou can rely on chrome/chromium => 70.
- solarkraft 8y ago> you won’t be able to use specific API for sure How about W3C standards?
- JeanMarcS 8y agoFor just visualizing your document, sure. I was thinking of my webkiosk software where Interfaces on Internet Explorer changed with version (but thankfully Microsoft provided compatibility). But as long as the Event / API / I don't really know how it works with Chrome / Whatever way to get the Before Navigate information (and be able to stop it) still works from a version to another, W3C standard would suffice for the majority of cases