I recall past developments where Google re-wrote the rule-book on what buttons could do which broke things for other browsers. Perhaps this might not be asChrome 135 introduces new capabilities for providing declarative behaviour with the new command and commandfor attributes, enhancing and replacing the popovertargetaction and popovertarget attributes. These new attributes can be added to buttons, letting the browser address some core issues around simplicity and accessibility, and provide built-in common functionality.
A kind reminder we would like all registered users to weigh in on one of our forum's security policies.
Please take a moment to read this thread and place a vote.
https://forum.palemoon.org/viewtopic.php?f=17&t=32935
Please take a moment to read this thread and place a vote.
https://forum.palemoon.org/viewtopic.php?f=17&t=32935
Is this going to lead to a fresh hell for those not on the Chromium-aide?
Moderators: trava90, athenian200
-
SlySven
- Apollo supporter

- Posts: 39
- Joined: 2018-07-07, 22:42
Is this going to lead to a fresh hell for those not on the Chromium-aide?
https://developer.chrome.com/blog/comma ... commandfor :
browserground-breaking as they claim but I don't write code for web-browsers...