Announcement
Collapse
No announcement yet.
Firefox 61 Releasing Today With Performance Improvements, Accessibility Inspector
Collapse
X
-
And I'm still stuck on version 58 because Firefox developers are too lazy to check the DNS server response to see if the web server's ip address is localhost and stop forcing HTPS on my virtualhost domain (.dev) based on HTTPS preload list.
Seriously, Firefox developers made web developers harder because of their lazyness and their policy to follow Google's shitty trends for their owned domains.
- Likes 2
Comment
-
Originally posted by Jeff99 View PostI can get behind most of these pretty strongly, but I am leaning pretty strongly away from CSDs. For floating (and IMO really only floating) WMs, they save space and can look nice, but they seem like a horrendous abstraction after any small amount of serious thought. If X and/or Wayland need protocol extensions for application windows to get more control of how WM/compositor decorations render, so be it, but not giving the broader environment primacy in managing windows opens up a lot of issues around application reliability and trustworthiness.
Comment
-
Originally posted by Danny3 View PostAnd I'm still stuck on version 58 because Firefox developers are too lazy to check the DNS server response to see if the web server's ip address is localhost and stop forcing HTPS on my virtualhost domain (.dev) based on HTTPS preload list.
Seriously, Firefox developers made web developers harder because of their lazyness and their policy to follow Google's shitty trends for their owned domains.
The best solution isn't ever going to be maybe changing our own local test domain from .dev to .test, which was for the domain we should have used to begin with, as since the very recent year of 1999 it is an officially reserved domain for testing. https://en.wikipedia.org/wiki/.test
- Likes 4
Comment
-
Originally posted by uid313 View PostThings I would like to see in Firefox:- ...
- Support for the <dialog> element. caniuse.com/#feat=dialog
...
Comment
-
Originally posted by coder View PostWTF do you want web pages opening dialog boxes? I'm sure their lack of support for that is intentional, and I consider it a feature.
The modern web uses dialogs extensively but does so using <div> element together with CSS and JavaScript.
The <dialog> element introduces a way to keep doing the same thing but in a more semantic way.
With a semantic element it will be even easier for you to block them if you consider them annoying.
- Likes 2
Comment
-
Originally posted by coder View PostWTF do you want web pages opening dialog boxes? I'm sure their lack of support for that is intentional, and I consider it a feature.
Have you ever clicked a button and wanted a confirmation prompt before it goes to do something or other? Yeah, that's a dialog.
Comment
Comment