Pablo,
No worries; I learned a long time ago that text doesn't accurately
portray tone, so I try to always give people
the benefit of the doubt online. Take that lesson to heart.
From [0] :
" Around 390,000 Firefox OS phones shipped last year, according to IDC,
a figure it expects to rise to 2.5 million this year. That will give
Firefox OS a 0.2 percent share of the total smartphone market, IDC
analyst Francisco Jeronimo said via email."
Any other questions about feature detection, email me directly. Feature
detection is kind of my thing, and
UA sniffing is like nails on a chalkboard for me.
[0]
http://www.pcworld.com/article/2094040/telefnica-partners-with-line-on-messaging-app-for-firefox-os.html
Thanks,
~Nick Desaulniers
Open Source Zealot
Mozilla Corporation
On 5/8/14 3:27 AM, Pablo Brasero Moreno wrote:
Wow, I wasn't aware you could test for CSS capabilities through the
`style` property. Thanks for that.
Actually Nick, thank you for your feedback in general. I apologise if
I sounded whiney by the way. My intention is to clarify these
questions, not to criticise the tremendous efforts that have been put
so far.
The figure of 400k phones is amazing. Has Mozilla (or others)
published this information somewhere, with any further details?
Thanks to all involved in this thread. It has indeed helped me
understand the situation better.
On 5 May 2014 22:19, <[email protected]
<mailto:[email protected]>> wrote:
Does `"flex" in document.createElement("div").style` not work?
Where does feature detection not work? I mean, flexbox still
isn't widely implemented anyways across browsers. [0]
I agree that we shouldn't have any mention of 1.2 for the
simulators [1].
Right now Mozilla doesn't have leverage over the carriers/handset
manufacturers to keep all devices supported forever; Google barely
does. It sucks and is shitty, but maybe our branding team could
start including such requirements. Locked bootloaders are also
pretty evil. But if we can get in this space with a non
insignificant marketshare, we can change the landscape. It's not
going to just change overnight. That's why we've been working on
a reference device where WE are in control, not hardware vendors.
Will that pan out? We will see...
For now, target 1.1. Soon, many devices will start shipping with
1.3 or receiving OTA updates. Ignore 1.2. If you're not happy
with MDN, it's a public wiki, edit where you see fit. The person
who says it cannot be done should not interrupt the person who is
doing it. Also, Feature Detection, Feature Detection, Feature
Detection. If you have trouble detecting support for some
feature, email me directly, and I'll work with you on finding a
way to support devices that don't have such a feature, or at least
fail gracefully on them.
The FxOS Release notes for developers are where we post API
changes between version. [2] I'm guessing you're looking for these.
If we sold 400k phones last year, I'm going to venture that most
of those weren't mostly to technical oriented folks, though I
don't think we have the market research to accurately describe our
actual customers.
[0] http://caniuse.com/#feat=flexbox
[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1004725
[2] https://developer.mozilla.org/en-US/Firefox_OS/Releases
_______________________________________________
dev-webapps mailing list
[email protected] <mailto:[email protected]>
https://lists.mozilla.org/listinfo/dev-webapps
--
Pablo Brasero Moreno
[email protected] <mailto:[email protected]>
_______________________________________________
dev-webapps mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-webapps
