As I said in one other post to this thread. We will be able to cherry
pick the warning we care about directly in Gaia.
You won't see them anymore in logcat too.
On 17/01/2014 12:05, Julien Wajsberg wrote:
Le 15/01/2014 18:24, Fabrice Desré a écrit :
On 01/15/2014 09:09 AM, Julien Wajsberg wrote:
CSS errors are another story, especially when we use CSS properties that
are prefixed/unprefixed and we try that the apps somehow load in other
browsers. But we definitely have some that needs to be fixed.
That doesn't apply to certified apps that have no chance of running
somewhere else. I cringe everytime I see a "syntax error, rule ignored"
coming from a core app.
So yes, please kill them all.
Actually, running our apps, even certified ones, in competing browsers,
can make it possible to use their tools too. You probably know some of
the competing browsers have quite neat tools that can complement
Firefox' tools.
Would it be possible to make Firefox not report unknown prefixed
properties if the unprefixed property is also specified?
_______________________________________________
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g
_______________________________________________
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g
