DEV Community 👩‍💻👨‍💻

Discussion on: Stay alert

Collapse
aubs profile image
Aubrey • Edited on

As a developer there is never a reason to use these antiquated (nonsensical and legacy) application flow functions. As developers we can easily implement the required functionality ourselves, ensuring our own application flow.

Let's put this into things/perspective users and developers can/should understand. (Noting; It actually currently only entails cross-origin iframe usage and a possible future complete removal from the spec).

  • As a user I do not want 3rd party scripts possibly pretending they are the site I am visiting; i.e. alert/confirm with clicks to some nefarious site => cross-origin-removal (what it is all about)
  • As a user I do not want a site/app possibly pretending they are the browser/os; i.e. alert/confirm with clicks to some nefarious site => complete-removal (what it will become)
  • As a developer I do not want to rely on "a" browser for my application flow. => complete-removal (what it will become)

As developers we should not accept that "old" is better, above "safer" is better. We live in a world wherein we know that the web is abused. As true developers we should all be behind this proposed change (spec from day1/not break the web arguments are superfluous as the current real world usage is mostly only nefarious cross origin scripts).

Are there really any real world examples of the usage? No; only tutorials. Tutorials are what they are; mostly always need to change to be applicable; given the weather. This is the weather.

A better possible integration could have been working towards an opt-in for legacy crap.

p.s.

A lot of people are stating nuclear silos confirm etc. The only real world apps which use these functions are already probably running on isolated browsers that are fixed (i.e. app built for IE 5.5). These apps are not nuclear silo apps; those run with VBasic ;-) Apart from tutorials there are no real world examples that merit the usage of these methods.

p.p.s. I wrote this fast on a mobile so I apologize for typ0s etc

Collapse
dmitriid profile image
Dmitrii 'Mamut' Dimandt

As developers we can easily implement the required functionality ourselves, ensuring our own application flow.

Can you point to an easy implementation that covers all this: ashleysheridan.co.uk/blog/Accessib...

"antiquated (nonsensical and legacy) application flow functions" have all that.

Collapse
nonissue profile image
Andy Williams

@aubs

As a developer there is never a reason to use these antiquated (nonsensical and legacy) application flow functions.

As a developer, you should realize that making sweeping and concrete assertions like this is complete folly, and reeks of hubris.