Given that the discussion in the issue is "hey let's use DNT/tracking protection as a signal to not load this", assume we're looking at a reasonable mitigation here and that this was at worst an oversight.
IE 10 and 11 support an earlier revision of CSS Grid via -ms-grid (old enough to still have prefixes!). You may be able to polyfill the basic support that way.
It's not presently possible to search across all files at once, but the Style Editor is one of the tools is due for an update to match the current Debugger tool which has a better interface!
> .. the current Debugger tool which has a better interface
Respectfully, I disagree. The debugger tool's search in files is klunky with the bang prefix required to search all files and the search results shown in a scrollable popunder panel. Search should operate over all files/nodes in the current tab's category by default. And, it is bad UX for a tool that itself is (usually) a docked panel in the main browser window to have temporary panes appear that crowd out or obscure their neighbors. You've already got a file tree on the left, why not make that a twisty tree and categorize the search results under their parent files there - that is, if you feel your developers must have fancy clicky bits.
For those interested, here's some related bugs to look at:
The comments in that Firebug gaps ticket hurt me to read. Firebug got shanked by you guys like over a year ago and Developer Tools aren't close to feature parity.
Dear Firefox product owners: developer tools have to be great for the boring use cases -AND- the sexy HTML5 debugging use cases. Please put more resources into the Firebug gaps ticket and knock that one out.
There's lots of great UX enhancements there! I'm so looking forward to this!
Is this really the "current debugger tool" though? It doesn't ship with Firefox yet, does it? It's vaporware to users until it's displayed in developer tools and WebIDE.
I really wish this new Debugger would not show search results as a popunder/panel replacement the way that devtools does though! You have a massive amount of precious screen real estate in the debugger already devoted to the script sources panel. Why wouldn't you just cycle through matches in the actual script sources where the most characters surrounding each search result can be viewed by the user? Not only is using the script sources as the viewer for search results simpler to code, but the user is not taken out of the flow of their script editor/viewer in order to cycle through the results they've requested. What's the usecase that is being satisfied by breaking the user out of the script editor here?
I work at Mozilla, but I'm excited about this because I'm a web developer!
If you've ever tried to use flexbox to align content across multiple rows (like laying out a form with labels), you'd know that it's not a true two-dimensional layout tool. CSS Grid is, and will likely supplant flexbox as a flexbox is merely a one row/column grid.
The inspector is a pretty handy way to see what's going on under the hood, and being able to see the line numbers and named areas is great for visual debugging.
I'm sure this is not the correct way to ask but still, I just logged in to ask you this: Can you guys please add this feature other consoles have where you can use the mouse scroll-wheel to add or substract to CSS properties on the console? IE. font-size, border size, width, etc.
1. Hello potch!
2. Yes, this is among the most requested features we've seen so far. Containers in Test Pilot will remain in active development for the foreseeable future, so I wouldn't be surprised to see such a feature forthcoming.
You can load any game written in BYOND in FireFox and have the performance issues show almost immediately.
But it's especially egregious in mine and I don't know why, as I've done almost nothing besides add a few basic extensions to the base engine to create a somewhat-usable 2D Second Life-esque platform (with far more expansion capability) and FF just dogs on it. Space Station 13 REALLY makes the problems stand out.
A URL to something that shows the problem really would be useful here. I can profile and all that, but it would be good to be profiling something that actually shows the problem.
Tell ya what, give me a few hours to unwind from my gig this morning and I'll see if I can't get my old server actually up and online and port-forwarded. If I can (this assumes I actually have spare ports on the router) I'll send you the link, as I see that No-IP just sent me a renewal notice for the game's domain name anyways.
"Progressive Web Apps" is a Google brand. It's made of some good best practices and great technologies, but they reserve the right to re-define it and change the rewards around it however they choose. Install buttons are the carrot, and search rankings are the stick. Will non PWA-compliant but otherwise fast, well-made mobile web sites rank as highly as PWAs?
Just a minor nit, yes we have been working under the Progressive Web Apps headline for a while (I work on the devrel team) but it is a shared term that Opera and Mozilla are using.
Search has no understanding of Progressive Web Apps to my knowledge. Performance, Mobileness (on mobile search) and TLS are all ranking factors of some sort.
The current way that we see the banner is that it is the equivalent of an App install banner for web sites that meet the rough idea of what a Progressive Web App is and would be something that you would want to install or act like an installed app on the system.
The thought at the time of the change wrt to the fullscreen or standalone is that to get that app like treatment in the OS you would expect it to launch as an app would on the system (sans-url bar).
Note: we are also thinking of ways to get the URL bar back to the user when it is launched standalone or in fullscreen. It's a complex UX problem but we want to get the best of both worlds.
I got a chance to try tiltbrush recently. I drew a little cottage around myself, complete with a table and couch. While I was painting the ceiling, I subconsciously stepped around my couch to avoid tripping on it. That's when VR clicked for me :)
My first time with VR I had a similar experience playing a driving sim on a friend's DK2. When I had finished playing I stood up out of the chair, ducking to miss the door frame
