Earlier quoted context omitted.
...
That would break HN.
Blink tag removed from Firefox
91–99 of 99 posts
Re: Blink tag removed from Firefox
#92Re: Blink tag removed from Firefox
#93All snark aside, I wonder what the rationale was for doing this. It'd be a shame to load a website in a browser 20 years from now, only to see the site render incorrectly due to no-longer-implemented tags. Next, ? It's tough, obviously, because we can't have cruft build up all over. But this seems like a fairly straightforward case that a browser could shim out in JavaScript by default. Blink is a pretty straightforw…
There were parameters threaded throughout random layout functions to record how long things were supposed to blink for. It was a maintenance burden.
Re: Blink tag removed from Firefox
#94Earlier quoted context omitted.
Like what? I buy the use case of using a table for data, but are you implying there's other scenarios where using table elements are the best choice?
Here's an example, for one: http://css-tricks.com/centering-in-the-unknown/ (talks about a CSS/divs solution, but as it mentions there are differences between the two). In general if you're dealing with a design that involves centering something with a dynamic size vertically, or one which involves having the height or width of two dynamic elements add up to the width of a third adjacent element (ie. "rowspan" and "c…
Re: Blink tag removed from Firefox
#95Earlier quoted context omitted.
Like what? I buy the use case of using a table for data, but are you implying there's other scenarios where using table elements are the best choice?
Email for one.
Re: Blink tag removed from Firefox
#96All snark aside, I wonder what the rationale was for doing this. It'd be a shame to load a website in a browser 20 years from now, only to see the site render incorrectly due to no-longer-implemented tags. Next, ? It's tough, obviously, because we can't have cruft build up all over. But this seems like a fairly straightforward case that a browser could shim out in JavaScript by default. Blink is a pretty straightforw…
I'm sure if it becomes well and truly missed, someone will make an add-on to interpret them properly.
Re: Blink tag removed from Firefox
#97Earlier quoted context omitted.
I would not be at all surprised if there was a high correlation between "People who turned off Javascript" and "People who declined to provide telemetry", so there could be some selection bias in those results.
People who understand what that setting did can still disable by going to about:config! This is not a conspiracy, just making browser hard to break for people who check boxes and forget about these. For those, browser is broken! Those who know what disabling JavaScript actually does still have a way to disable! Where does all the privacy talk come in between?
When I got my last company laptop without all these things set, I was surprised how painful it was to try and download anything without a proper adblocker and noscript. I don't know how people do it.
Re: Blink tag removed from Firefox
#98Earlier quoted context omitted.
I'm using SlickGrid[1] in an internal tool. It uses divs and spans to display data, so there are certainly nice examples that do so. 1. https://github.com/mleibman/SlickGrid
But why would you want that? The whole point of moving from to for layout was that using wasn't semantic and was the wrong tool for the job. But is the right tool for displaying tabular data. That's its entire purpose for existing. Using to display tabular data is a regression. Edit: typo
On the other hand, I like the idea of less and more generic constructs that can be adapted to achieve some need. Specialized tags like dd, address, details, summary, code, blockquote, etc just seem superfluous.
Re: Blink tag removed from Firefox
#99Earlier quoted context omitted.
there's bugs for each of these (which are open to the world and anyone can comment) all you have to do is to take a stance during the process. harder to do so after a bunch of various people (employed or not by mozilla) decided something. pretty sure those options went off because enough people decided that the preferences/option panel was too complicated and these were the ones that telemetry indicated were the leas…
I would not be at all surprised if there was a high correlation between "People who turned off Javascript" and "People who declined to provide telemetry", so there could be some selection bias in those results.