> the following individuals have contributed to this specification
> Mary Ellen Zurko
Literally the second specification I opened had one woman in the "Acknowledgments" section.
Maybe try at least using the HTTP protocol to search the web once before spewing absolute nonsense that doesn't even try to add something, only detract.
Asahi and GNOME teams, please take this as an guide to implement ”Mac input compatibility mode”!
Dual booting between a MacOS and Linux is a painful process of manual keyboard and shorcut overrides to get the linux side somewhat to the (better) mac way of doing this.
Omarchy does a pretty good job of this. Super+C, Super+V works everywhere, even the terminal in a consistent way. But there are exceptions to super acting like MacOS command, like if you want to select all, then copy you have to do the Ctrl+A, Super+C jujitsu.
Atleast some EU countries have ”strong authentication” services, which work like Google login, except there’s a network of trusted providers - like banks or telecoms.
To get started, you need get an account at one of the providers by physically visiting their store or office and show your ID. With their account you can sign up to the services or other auth providers fully online. Auth providers use 2-factor auth (typically website username + phone app), but they also include physical sim cards or key generator devices…
Anyways, while it’s currently used to pass some required personal info to the other party (name, social security number), it could propbably be changed to send just one bit: adult true/false.
Your cheesing startegy sounds more like what would actually happen in movies, where the protagonists get a last minute dangerous idea to skip jump past the overwhelming enemies and save the day…
Funnily enough doing it yourself in the game may feel like just cheating, but watching a movie one would be celebrating along.
The is="" customized-built-in path (extends HTMLButtonElement) is exactly what would collapse that 500-line reimplementation. Safari refusing it is why you still fall back to a full autonomous element + ElementInternals.
The only browser Apple is blocking it on is Safari: other browsers implement it just fine, and the standard passed over Apple's objections. The rationale was architectural, arguing that extending built-in components would lead either to brittle components that would break when new properties were added or causing the specification of builtin components to freeze forever to avoid such breakage. I'm not sure I buy the arguments 100%, but for sure it's not evil/incompetent board executives twirling their mustaches as they deliberately break the web: https://github.com/WICG/webcomponents/issues/509#issuecommen...
This is sort of correct on webkits side. inheritance chains especially when you don't control who is inheriting from you are going to be very brittle. The standard would probably have been better if it had been specified as a form of composition instead. However not supporting something like this is largely worse than just doing the inheritance. I'm not sure this is a hill I would die on despite largely agreeing with the webkit folks here philosophically.
That's my take on it too. The DOM itself is full of issues from its naive inheritance-happy OO design, and could use a refresh into something with better separation between data and presentation, but it's what we have right now in the real world. There's always going to be footguns, we can't put safeties on all of them. I have to wonder if it's something in the design of WebKit that makes inheritance particularly difficult to implement.
As for potential property collisions, I think the common wisdom is to just ensure the property name contains a dash, since the html5 spec goes out of its way to avoid using them. Doesn't solve brittle inheritance hierarchies in general, but it does at least stay out of the way of built-in behavior.
Would love to hear their thoughts and visions of what the web could be at the time.
reply