3 ms·

I don't have a link, it was a Mozilla evangelist at a live event who was showing off the 'new' 3D abilities. And I did file a bug. The first reply was: "this sh

by unconed 15y ago

I don't have a link, it was a Mozilla evangelist at a live event who was showing off the 'new' 3D abilities. And I did file a bug. The first reply was: "this should be split up into multiple bugs" with no further information. Apparently, submitting a simple use case from the end-user's perspective is frowned upon and we should all know the internals of Firefox so we can file code-oriented bugs appropriately. Further commenters were more helpful, but I can't say I was one bit surprised. As for the mobile web... even my WebKit Android browser fails often, even on this very text field. There is no single 'webkit for mobile', and it's all the non-iPhone users that are treated as second class citizens, webkit prefixes or not. That's IMO a very different problem. As for WebKit2, you're right, that was badly worded. What I meant was "the Safari engine since they switched to WebKit2" (i.e. Lion). It came with a noticeable improvement in rendering performance, which Chrome has not been able to match on any system I've tried. Ultimately it all comes down to opinion and perception. But I have a hard time finding people who are still excited about Firefox who aren't Mozillians.

azakai 15y ago
> As for the mobile web... even my WebKit Android browser fails often, even on this very text field. There is no single 'webkit for mobile', and it's all the non-iPhone users that are treated as second class citizens, webkit prefixes or not. That's IMO a very different problem. It's the same problem, and it's just as bad: If there is one dominant implementation, and other browsers can't render the actual web even when they implement the relevant standards - then the web is broken. If it's WebKit vs the rest or iOS vs the rest, it's just as bad. Regarding your frustration on the Mozilla bug tracker, I've definitely felt that both there and basically on every other major bug tracker. The other day I filed a bug on Node.js, and in 15 minutes there were three responses, saying things like "why is this a bug in node?", "don't file bugs on node like this", and soon after the bug was closed. A few days later, it was confirmed as valid... that's how it goes in big bug trackers ;) > Ultimately it all comes down to opinion and perception. But I have a hard time finding people who are still excited about Firefox who aren't Mozillians. I have very much the opposite impression, we probably just visit different websites and communities.

by unconed 15y ago

azakai 15y ago

> As for the mobile web... even my WebKit Android browser fails often, even on this very text field. There is no single 'webkit for mobile', and it's all the non-iPhone users that are treated as second class citizens, webkit prefixes or not. That's IMO a very different problem. It's the same problem, and it's just as bad: If there is one dominant implementation, and other browsers can't render the actual web even when they implement the relevant standards - then the web is broken. If it's WebKit vs the rest or iOS vs the rest, it's just as bad. Regarding your frustration on the Mozilla bug tracker, I've definitely felt that both there and basically on every other major bug tracker. The other day I filed a bug on Node.js, and in 15 minutes there were three responses, saying things like "why is this a bug in node?", "don't file bugs on node like this", and soon after the bug was closed. A few days later, it was confirmed as valid... that's how it goes in big bug trackers ;) > Ultimately it all comes down to opinion and perception. But I have a hard time finding people who are still excited about Firefox who aren't Mozillians. I have very much the opposite impression, we probably just visit different websites and communities.