2) Common website features are rolled into the web standards. E-mail enrollment requests, GDPR notices, interstitials, etc., should all be supported as features at the browser level, not the site level.
-
-
Show this thread
-
3) Websites are precluded by the standard from implementing custom user authentication. All authentication is handled by the browser with the support of the operating system. (PKI. Like using your Apple ID / Face ID to log into Facebook.)
Show this thread -
4) Websites are not allowed to side-load content from another domain without express consent from the user. (i.e. No surreptitious javascript or cookie tracking, redirects, etc.)
Show this thread -
5) When the website needs to store data about you, the best practice is to store that data on your local machine, rather than on their server. When the site later needs to access that data, the browser requests your permission first.
Show this thread
End of conversation
New conversation -
-
-
CSS was originally envisioned so that the site would send a default stylesheet which the browser overrides according to user needs and preferences. Allowing sites to send their own styles turned out to be a pretty bad idea.
-
User stylesheets set in the browser do override all other styles. There’s just no friendly interface for managing or creating one.
-
As a user, I can’t even begin to imagine trying to override that shit-markup soup and pretty much guaranteed non-existent document structure.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.