Mozilla removes -moz-opacity; man threatens to sue for $18,000
bugzilla.mozilla.org
bugzilla.mozilla.org
Also, duuuude, the site in question is awesome: http://www.constellation7.org/Constellation-Seven/Josiah/Ind...
search and replace anyone?? carefully crafted query using even Funduc S&R would take it max 5 minutes... but hey, given the content of the site... I would be afraid of a guy quoting bible verses in replies too!
http://www.thefreedictionary.com/YHWH http://dictionary.merriam-webster.com/dictionary/yhwh
It is a weird phenomenon and it usually has the opposite effect on me because it shows that the person doesn't even understand what his/her own religion is supposed to be about.
(Note: I am a Christian myself)
I think we've just found this generation's TimeCube.com
"Java needs your permission to run."
"Flip4Mac needs your permission to run."
"The page at www.constellation7.org says..."
Yikes.
BTW, can't they just leave the legacy behaviour in quirks mode only or does slimness and catching Chrome trump functionality?
This make 1986 Print Shop hot shots look like Michelangelo in comparison.
Edit: OH DEAR LORD look at their web page!!!
This site might be useful to the internet as the canonical web design anti-pattern repository.
emphasis mine.
"HONESTLY, it's just plain senseless destruction of a set of attractive visual effects that should be ALLOWED to be seen...."
edit: https://bugzilla.mozilla.org/show_bug.cgi?id=765645#c10
I think we should give this person the benefit of doubt and treat him/her like a troll.
Why do these guys even bother to give people like this the time of day?
Think that with a discount, US$18,000 should be sufficient to cover all my time related costs, fixing ALL code instances, for ALL the aforestated reasons..."
Then he adds:
"Thanks a bunch for being SO HELPFUL !!!"
Also, $18,000/$247.00/hour comes out to about 72 hours.
His first post was on 2012-06-17 21:06:44 PDT and his last post was on 2012-06-19 23:11:22 PDT, so it's only been ~50 hrs since he posted it until he asked for the money.
This one made me chuckle
> Ideally, ALL browsers SHOULD support ALL extensions,
I don't think he quite gets it.
But the title of this post is a bit inaccurate in that he didn't threaten to sue. He threatened to send Mozilla an invoice for his work, but he came out looking very foolish, and ended up tucking tail.
1. The prefix was already not being supported by most browsers, thus supporting it would mean supporting the development of websites that don't work properly in other browsers.
2. Best practices suggest that one shouldn't rely solely on the prefixed version of an experimental alias. If this developer had written good code to start with, he wouldn't have had the problems he ran into.
They don't want to tie people to Firefox. So when a standards-compliant version of a CSS directive becomes available, they deprecate their own -moz version. Eventually they remove it.
The goal statement is that a page written using Firefox as the development browser will look the same for Chrome, IE and so on.
-moz defeats that purpose because it's browser-specific.
Here's an example I blogged about a while back: http://blog.tommorris.org/post/6898909918/quoted-for-hilario...
Minus the extortion of course.
So I doubt it. I'd love to believe it, but I doubt it.