| Their tags shall blink until the end of days.
from The Book of Mozilla, 12:10
Blink tag removed from Firefox
51–60 of 99 posts
Re: Blink tag removed from Firefox
#52Earlier quoted context omitted.
Let this day go down in history as the day we declared our independence from the tyrannical Mozilla organization and their corporate-interest driven and oppressive removal of our freedoms and ability to customize our browser. We shall not be stricken down by their restrictive and non-representational releases of firefox... instead we choose to be empowered by the option to disable things such as javascript, and tabbe…
If you don't like the direction the Mozilla Corporation is taking Firefox, you're free to disable automatic updates, revert to a previous version of the browser, or even fork your own version of Firefox. It's not tyrannical to want new versions of Firefox to present a better user experience and be less confusing to everyday users.
... and not receive security patches.
Re: Blink tag removed from Firefox
#53All 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…
Keep a VM with a vintage browser along for the ride, I have a feeling blink tags won't be the only thing different in 20 years.
Re: Blink tag removed from Firefox
#54Earlier quoted context omitted.
Yeah, they're trying to remove the settings that people set to goof up their browsers from the look of this. There's this one, too: "Load images automatically" and Always show the tab bar" checkboxes removed from preferences and reset to defaults
Let this day go down in history as the day we declared our independence from the tyrannical Mozilla organization and their corporate-interest driven and oppressive removal of our freedoms and ability to customize our browser. We shall not be stricken down by their restrictive and non-representational releases of firefox... instead we choose to be empowered by the option to disable things such as javascript, and tabbe…
You can still disable it from about:config, drama queen.
Re: Blink tag removed from Firefox
#55Earlier quoted context omitted.
Exactly, and if you're so inclined to have those options set in a certain (and don't want to do so through some other addon like NoScript) you can set it in about:config.
The primary problem is that the about:config flag for hiding tabs is ineffective so there is more to the solution than just looking deeper into the config menus. I agree that these options are for power users, but my fear is that soon after they relegate the ability to disable javascript to the bowels of the application, they will soon remove it entirely. And that this decision is in fact not driven just by the fact…
[deleted]
Re: Blink tag removed from Firefox
#56Earlier quoted context omitted.
There are still use-cases where using is the cleanest way to achieve something without resorting to javascript (or a soup tag).
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 "colspan" in table-speak), there's a decent possibility that using a table might just be the least-hacky way to implement something. Bearing in mind that hackiness is a bit subjective :)
Re: Blink tag removed from Firefox
#57Aww, man. I love using (in FF) and (in Chrome) when giving presentations, they're such crowd pleasers. At least Chrome still has , I used it in a talk just 2 days ago. Hope they don't follow FF's lead.
Are you trying to drive your audience to distraction?
Re: Blink tag removed from Firefox
#58Earlier quoted context omitted.
Let this day go down in history as the day we declared our independence from the tyrannical Mozilla organization and their corporate-interest driven and oppressive removal of our freedoms and ability to customize our browser. We shall not be stricken down by their restrictive and non-representational releases of firefox... instead we choose to be empowered by the option to disable things such as javascript, and tabbe…
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…
Bugzilla is not your personal soapbox. The revolution is a damp squib.
Re: Blink tag removed from Firefox
#59What a fitting farewell. If you check the source, the item is wrapped in the old blink tag.
`Dropped blink effect from text-decoration: blink; and completely removed element `
Start up firefox and give it a nice sendoff.
Re: Blink tag removed from Firefox
#60Earlier quoted context omitted.
Let this day go down in history as the day we declared our independence from the tyrannical Mozilla organization and their corporate-interest driven and oppressive removal of our freedoms and ability to customize our browser. We shall not be stricken down by their restrictive and non-representational releases of firefox... instead we choose to be empowered by the option to disable things such as javascript, and tabbe…
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.