Mozilla in 2013
blog.mozilla.org
blog.mozilla.org
You're complaining about lack of some edge-css features, silly bugs that have been open for a long time, and the fact that they may be chasing down some avenues that yield little fruit.
But, the web I envision without them is one that I do not want any part of. While I switched and used Chrome (for the tools), lately, the only browser vendor that I trust is Mozilla. I switched back to FF, donated, and decided to start dipping into their code/docs to see if I can help out.
While certainly not perfect, they are the company that we should be supporting. Not necessarily financially, but by being advocates, code/doc junkies and designers.
Here's to Mozilla and here's to 2014. Congrats!
We are working to set up a gear store. Hopefully, we'll be able to announce it early in the new year.
In the meantime, if you know someone who is an e-commerce / systems integration expert, please point them at this opening:
http://careers.mozilla.org/en-US/position/oOP3Xfwn
Thanks,
G.
Anyway thanks for the link that's what I was looking for.
If GoG doesn't need my address why would Mozilla? And further more why should it complain about wrong address.
Hell, smaller companies asked for address but never checked it against my CC info (which is outdated anyway). I never had to enter the correct address for one of them.
I want to donate, but this form just bounces me I've so far tried at least 10 different combinations. I have no idea what bank entered as its information.
My understanding of the system is that usually the address can be wrong so long as your card/connection/purchase/etc doesn't look suspicious, but different payment processors have different fraud profiles, so some might pay more attention to the address than others.
This early sentence really derailed me. There is so much going on:
-What is an "open web device", what qualifies? Maybe put a link here?
-Why is Firefox OS called an OS if it is actually devices?
-Is being based IN web technologies the same as being based ON web technologies?
-And there is a weird implication here that there have been open web devices NOT based on web technologies but now we have open web devices that actually ARE based on web technologies. That can't be right, can it?
From what I can tell the sentence should read something like, "In 2013 we launched Firefox OS, the first [mobile?] operating system based entirely on Web technologies."
"Web device" implies a device that allows browsing the web (such as a smartphone or tablet). "open" implies that it is open source to some extent (similar to Android).
"based entirely on web technologies" differentiates it from Android in that all apps are web apps and use standardized web APIs to access the hardware rather than having native apps that use proprietary APIs.
It does seem weird that the sentence use the term "OS" to describe devices, though.
[1] https://en.wikipedia.org/wiki/Mozilla_Corporation#Google
And if it weren't for Firefox, you'd still be developing for IE6.
I'm sure that they care about those bugs, but right now the major battle for everyone is in the mobile platform area. If Firefox OS doesn't gain a foothold we're basically in walled garden area forever (even though Android is OSS I don't trust Google to not become reactionary once the market is saturated and Android dominates it; and through patents + branding Google can still prevent major forks if it wants to).
So for your own long term sake, you'd better wish that they do make it, even if they have to postpone a few CSS bug fixes.
My cringe with Firefox are misfeatures like window.onbeforeunload. They deliberately break the expected behavior due to an unreasonable decision, but no browser is perfect.
They tried a fix and it broke YouTube. So it seems like a reasonable fear. https://bugzilla.mozilla.org/show_bug.cgi?id=349259#c54
> The patch ... is literally to remove "!important" from one CSS file
It isn't a simple one line fix, as Firefox developer kindly explained. https://bugzilla.mozilla.org/show_bug.cgi?id=349259#c76
>That patch would not be welcome.
They describe what work would be required (and where the changes would likely be) for the patch to be accepted in the bug. https://bugzilla.mozilla.org/show_bug.cgi?id=349259#c80
Problem is, not everybody knows C++. Having a bug open for 7 years makes me think the issue will never be resolved. All I can do is wait or use another browser. One annoyance I have with Firefox is the lack of built in keychain support. This really summarizes how I feel: https://bugzilla.mozilla.org/show_bug.cgi?id=106400#c94
As for the original bug, this post: https://bugzilla.mozilla.org/show_bug.cgi?id=349259#c82 seems to suggest every browser but Firefox supports changing line-height. Wouldn't Firefox be going against the expected behavior?
If no one can even provide that...
-Accept cryptocurrency donations; -Break free from Google/surveilance as default search; -DDGo as default search; -Firefox OS becomes as adopted as iOS and Android; -Firefox browser regain market share back from Chrome/surveillance.
And it doesn't really matter what browser I was using at the time. Chrome, Firefox, even Safari.
What do you want to make your browser better?
I would love to see more features along those lines, such as de-pagination and blocking popover psuedo-windows. However as Firefox is funded indirectly through advertising, Mozilla's loyalties are necessarily mixed.
I could go on and on.
Goes off to file a bug...
CSS Grid implementation will start in 2014. A dev has been assigned to it, but I don't know where it stands in its work pile (quite high though). But plans can be changed, so beware...
> stable spec
I'd really like to see more vendor prefixes for support. I mean, basic flexbox support was rolled out quickly, and the spec changed like three times. Mozilla has a new 'avoid vendor prefixes' thing, which I think is the wrong approach. I'd rather just use a tool like autoprefixer to generate all of the browser-incompatible CSS until we can all agree.
I can't believe I am praising IE for being forward thinking! (they have full CSS grid support, per the draft)
Also grid isn't really a case of IE being forward thinking, Microsoft just happened to create the grid spec, so it's more a case of pushing their own solution, rather than being fast on implementing a new tech.
It does seem like a neat spec though, I’d welcome inclusion as another tool in the box.
FWIW, Google Blink also takes this position: http://www.chromium.org/blink#vendor-prefixes
Thank god for Mozilla, they are one of the few tech companies I still trust in these troubled times.
I like to think if the NSA asked for direct access to their servers (such as Google were revealed to have granted), Mozilla would have no shortage of whistle-blowers.
But a later Snowden leak showed that the NSA was tapping Google's fiber in a way consistent with the extra information we knew they were getting for PRISM, so Google appears not to have lied about that after all. The codename for the tap is apparently MUSCULAR[1].
Google is still totally turning over tons of data to the NSA under PRISM[2], but that goes through Google's lawyers and the court system so bad as it is, direct server access is much worse.
[1]http://arstechnica.com/tech-policy/2013/10/new-docs-show-nsa...
Mind posting a source confirming this? It's just that I don't believe you is all.
There are a lot of Google employees on HN who try to suppress information whenever anyone posts sources. Pretty pitiful.
"Although the presentation claims the program is run with the assistance of the companies, all those who responded to a Guardian request for comment on Thursday denied knowledge of any such program."
The PR response from Google is irrelevant, just attempting a cover up.
Seems level-headed and reasonable.