Re:Blink tag removed from Firefox
by mcav on Wednesday August 07, 2013 @12:15AM
(#6170785)
All 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, <center>?
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 straightforward piece of internet history. It's not like <applet>, which, while also a piece of history, actually carries legitimate complexity/security risks.
Re:Blink tag removed from Firefox
by mcpherrinm on Wednesday August 07, 2013 @12:35AM
(#6170857)
Gecko was, afaik, the last major browser engine that supported <blink>. Chrome and IE don't, at least. Opera won't, after switching to, ironically enough, the engine called Blink.
So it's not exactly the same as removing <center>: Other browsers already didn't support it.
Re:Blink tag removed from Firefox
by jacobr on Wednesday August 07, 2013 @03:17AM
(#6171321)
Oddly enough Chrome/Blink still has the String.prototype.blink method to create a blink tag from a string. If I recall correctly it's actually part of an ES (not DOM) standard.
Re:Blink tag removed from Firefox
by Bockit on Wednesday August 07, 2013 @04:50AM
(#6171602)
Wow. Because this surprised me so much, I just found out that if you open up a node REPL and type 'hello'.blink() you get '<blink>Hello</blink>' returned. So I guess it's an ES thing and it boggles my mind.
I was trying to find the ES standard where it's specified but I'll settle for this[1] instead. Interestingly enough you have quite a few HTML wrapping functions as part of the spec.
Re:Blink tag removed from Firefox
by Kequc on Tuesday August 06, 2013 @11:49PM
(#6170704)
The people that disable javascript either do it by accident and then stop using the browser or are nerdy enough to figure out how to turn off javascript in the configs. Javascript will also be configurable using plugins.
Re:Blink tag removed from Firefox
by panhandlr on Wednesday August 07, 2013 @12:26AM
(#6170827)
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 tabbed browsing because we understand these options to be self-evident truths for all browser users.
I am tired of having my freedoms stripped from my browser without any representation into the process. As a user of the browser I was not adequately informed of the upcoming changes nor was I given an opportunity to choose not to upgrade.
THIS MUST END
Contact me for further information, the revolution begins today.
Re:Blink tag removed from Firefox
by ryanpetrich on Wednesday August 07, 2013 @12:35AM
(#6170859)
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.
Re:Blink tag removed from Firefox
by sp332 on Wednesday August 07, 2013 @07:06AM
(#6171978)
Version 17 is the Extended Support Release and still gets security patches. Or, "I had those security holes right where I wanted them! Quit breaking my browser grr!"
Re:Blink tag removed from Firefox
by zobzu on Wednesday August 07, 2013 @12:36AM
(#6170862)
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 least used.
Re:Blink tag removed from Firefox
by caf on Wednesday August 07, 2013 @03:11AM
(#6171304)
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.
Re:Blink tag removed from Firefox
by Natsu on Wednesday August 07, 2013 @11:02PM
(#6177123)
NoScript is a much better option all around. I know I've been using it since forever.
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
by panhandlr on Wednesday August 07, 2013 @01:06AM
(#6170969)
This is no joke brother... We will not rest until this issue is heard in the highest of courts.
First they came for our <blink> tags and we laughed... then they came for our options to disable tabbed browser, and they said nothing... then they came for our option to not be tracked by online advertising agencies (javascript) and everyone was too busy sharing kitten photos on facebook to say a damned thing.
Re:Blink tag removed from Firefox
by pitterpatter on Wednesday August 07, 2013 @12:39AM
(#6170871)
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.
Re:Blink tag removed from Firefox
by panhandlr on Wednesday August 07, 2013 @12:58AM
(#6170933)
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 that it is seldom used, but driven more-so by the corporate interests they hold with advertising and other online entities that serve not for the browser users, but their own corporate interests. This fundamentally collides with the intent of the Mozilla foundations purpose and this behavior must stop.
The ability to disable javascript has been on the main screen of the options panel because it serves a very important purpose.
Also the ability to not show tabs when browsing a single web page because for that use case, it is more optimal to not show a tab and waste the screen real estate on dead space.
They have fundamentally altered the Firefox browser in a fundamental way that is not configurable and have not provided reasonable alternative.
I refuse to accept any so called "Add-On". These features are not to be pushed off into to the extremities of the community and be forgot about. I firmly believe that any such browser serving only the interests of the user would see these features as being non-optional options and should exist in perpetuity for the life of that software.
Re:Blink tag removed from Firefox
by notatoad on Wednesday August 07, 2013 @01:31AM
(#6171052)
Tab bar will be always visible. The fact that you have to ask means nothing, because you are one person. Decisions get made based on data, not anecdotes.
Re:Blink tag removed from Firefox
by plorkyeran on Tuesday August 06, 2013 @11:57PM
(#6170735)
NoScript continues to work fine and is much more functional than globally turning off JS. Anyone who intentionally turned off JS via the Firefox options will probably benefit from being forced to use NoScript instead anyway.
Re:Blink tag removed from Firefox
by pbhjpbhj on Wednesday August 07, 2013 @04:42AM
(#6171582)
Personally I've set - for as long as I recall - the javascript options in the submenu all off. I don't see why a page should be able to move windows or change default menus. I'm assuming these options are being removed from the GUI too. What are the defaults (they're not mentioned on the OP's page).
NoScript doesn't appear to have these fine tuning options?
Re:Blink tag removed from Firefox
by pamelafox on Wednesday August 07, 2013 @12:29AM
(#6170839)
Aww, man. I love using <blink> (in FF) and <marquee> (in Chrome) when giving presentations, they're such crowd pleasers. At least Chrome still has <marquee>, I used it in a talk just 2 days ago. Hope they don't follow FF's lead.
Re:Blink tag removed from Firefox
by skeletonjelly on Wednesday August 07, 2013 @04:44AM
(#6171587)
Marquee caused a whole bunch of CSS errors in a website I delivered. Client found out you could run code via onscroll, and the CMS I used (DNN) didn't filter it out. Ugh!
Re:Blink tag removed from Firefox
by Luyt on Wednesday August 07, 2013 @07:45AM
(#6172120)
I found BLINK and MARQUEE so infuriating irritant that I used to binary patch them out in the browser executable. This was before the era of signed executables.
(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
by proexploit on Wednesday August 07, 2013 @03:13PM
(#6174951)
Yeah certainly, thanks for the examples. I think the first item you mentioned, vertical centering of a single dynamic object actually can be handled better than tables currently (see some techniques here: http://html5hub.com/centering-all-the-directions/) but when you add more elements into the mix I can see how rowspan / colspan equivalents are not easily implemented without JS.
Re:Blink tag removed from Firefox
by statictype on Wednesday August 07, 2013 @03:15AM
(#6171317)
A main content area and a sidebar with each having different colors and both maintaining the same height such that they expand vertically with the content (without having to hard-code pixel values).
I saw a page showing how it could be achieved using only divs, but really, it was a complete rube goldberg machine, the sole purpose of which, seems to be to adhere to the religion of not using tables.
I get that table layouts have their own issues but I think its silly to be dogmatic about refusing to use them where it's clearly the best hammer to drive in that nail.
Re:Blink tag removed from Firefox
by krapp on Tuesday August 06, 2013 @11:45PM
(#6170692)
You're right, everything else I can think of is worse for data, tables are pretty good for that (minus the weird vertical centering thing that sometimes happens in cells.)
But seeing tables being used for layout annoys me far more than the blink tag.
Re:Blink tag removed from Firefox
by jallmann on Wednesday August 07, 2013 @12:01AM
(#6170749)
> But seeing tables being used for layout annoys me far more than the blink tag.
How come? CSS positioning is pretty unintuitive, and sometimes it's just easier to get something working with tables. If the end results look fine, what's the problem? Table-based layouts aren't in-your-face like the blink tag was.
Re:Blink tag removed from Firefox
by pamelafox on Wednesday August 07, 2013 @12:32AM
(#6170846)
When I rewrote the Coursera discussion forums and sent them through an accessibility audit, I was told to use <li>s instead of <div>s to represent the nested conversations, which makes a lot of sense when you think about it. Disqus also uses <li>s for their comments.
So, just FYI, if you find yourself generating HTML for something like HN anytime in your life.
Re:Blink tag removed from Firefox
by krapp on Wednesday August 07, 2013 @12:18AM
(#6170800)
My problems are mostly how easy it is to get lost if you're dealing with nested tables within tables (especially inside templates), and that they have to be completely read before rendering... although that may no longer necessarily be an issue with modern browsers.
I find divs and spans easier myself but I guess, yeah, at the end of the day if it looks fine and it loads fine then it's fine. Too much pain from hand-coding too many tables has made me twitchy and curmudgeonly.
Oh, and don't view-source on HN ;)
Oh, i'm aware...
It's just too bad html doesn't provide elements that handle nested lists. If only. Ah well.
Re:Blink tag removed from Firefox
by adrusi on Wednesday August 07, 2013 @12:47AM
(#6170899)
I've actually found CSS layout to be more intuitive than tables. maybe it's just that I have ages more experience with CSS than tables, but seriously, tables feel like a cludge for layout.
Re:Blink tag removed from Firefox
by glesica on Wednesday August 07, 2013 @12:27AM
(#6170833)
But why would you want that? The whole point of moving from <table> to <div> for layout was that using <table> wasn't semantic and was the wrong tool for the job. But <table> is the right tool for displaying tabular data. That's its entire purpose for existing. Using <div> to display tabular data is a regression.
Re:Blink tag removed from Firefox
by chucklarge on Wednesday August 07, 2013 @11:19PM
(#6177175)
I don't disagree, just pointing out that there are ways to achieve a tabular layout without an html table. Tables are for data right?
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
by mcpoulet on Wednesday August 07, 2013 @04:53AM
(#6171610)
I love the fact that in the release notes page, they used a <blink> tag around the message "Dropped blink effect from text-decoration: blink; and completely removed <blink> element".
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 straightforward piece of internet history. It's not like <applet>, which, while also a piece of history, actually carries legitimate complexity/security risks.
So it's not exactly the same as removing <center>: Other browsers already didn't support it.
I was trying to find the ES standard where it's specified but I'll settle for this[1] instead. Interestingly enough you have quite a few HTML wrapping functions as part of the spec.
[1]: http://javascript.spec.whatwg.org/#string.prototype.blink
"Enable JavaScript" preference checkbox has been removed and user-set values will be reset to the default
"Load images automatically" and Always show the tab bar" checkboxes removed from preferences and reset to defaults
I am tired of having my freedoms stripped from my browser without any representation into the process. As a user of the browser I was not adequately informed of the upcoming changes nor was I given an opportunity to choose not to upgrade.
THIS MUST END
Contact me for further information, the revolution begins today.
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 least used.
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.
https://socialcam.com/v/39HPvZde
Protesters can be heard chanting:
"WHAT DO WE WANT?"
"The ability to disable tabbed browsing"
"WHEN DO WE WANT IT"
"Possibly in the next point release, but the next major is cool too"
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 that it is seldom used, but driven more-so by the corporate interests they hold with advertising and other online entities that serve not for the browser users, but their own corporate interests. This fundamentally collides with the intent of the Mozilla foundations purpose and this behavior must stop.
The ability to disable javascript has been on the main screen of the options panel because it serves a very important purpose.
Also the ability to not show tabs when browsing a single web page because for that use case, it is more optimal to not show a tab and waste the screen real estate on dead space.
They have fundamentally altered the Firefox browser in a fundamental way that is not configurable and have not provided reasonable alternative.
I refuse to accept any so called "Add-On". These features are not to be pushed off into to the extremities of the community and be forgot about. I firmly believe that any such browser serving only the interests of the user would see these features as being non-optional options and should exist in perpetuity for the life of that software.
Which way I'd this one going to go? On or of? And the fact that I have to ask tells me that maybe they should not have removed the option.
Personally I'm glad it's in the visible direction though.
An option should only be removed if the "better" way is obvious.
NoScript doesn't appear to have these fine tuning options?
`<blink>Dropped blink effect from text-decoration: blink; and completely removed <blink> element </blink>`
Start up firefox and give it a nice sendoff.
The idea was first discussed at a bar in Mountain View, CA.
[1] http://www.montulli.org/theoriginofthe%3Cblink%3Etag
from The Book of Mozilla, 12:10
( http://www.vice.com/read/its-now-possible-to-hire-fake-prote... )
The lack of it was the last thing that was keeping me using Firebug.
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 :)
I saw a page showing how it could be achieved using only divs, but really, it was a complete rube goldberg machine, the sole purpose of which, seems to be to adhere to the religion of not using tables.
I get that table layouts have their own issues but I think its silly to be dogmatic about refusing to use them where it's clearly the best hammer to drive in that nail.
But seeing tables being used for layout annoys me far more than the blink tag.
How come? CSS positioning is pretty unintuitive, and sometimes it's just easier to get something working with tables. If the end results look fine, what's the problem? Table-based layouts aren't in-your-face like the blink tag was.
Oh, and don't view-source on HN ;)
So, just FYI, if you find yourself generating HTML for something like HN anytime in your life.
I find divs and spans easier myself but I guess, yeah, at the end of the day if it looks fine and it loads fine then it's fine. Too much pain from hand-coding too many tables has made me twitchy and curmudgeonly.
Oh, and don't view-source on HN ;)
Oh, i'm aware... It's just too bad html doesn't provide elements that handle nested lists. If only. Ah well.
as a <table> user, I feel vindicated :P
1. https://github.com/mleibman/SlickGrid
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.
http://cheese.blartwendo.com/web21-demo.html
;)