In general, how should we mark those nice-to-have bugs to raise awareness?
I'd suggest marking them as blocking the corresponding B2G bugs. Also,
not committing a hack in Gaia to fix a Gecko bug is a strong incentive
(you have to balance this with deadlines of course).
For devtools, we created a meta-bug:
https://bugzilla.mozilla.org/show_bug.cgi?id=gaia-devtools.
On 22/08/13 18:56, Kevin Grandon wrote:
Additionally this would be really nice to have for select elements:
https://bugzilla.mozilla.org/show_bug.cgi?id=649849
We currently have some really nasty workarounds for this in gaia.
-Kevin
----- Original Message -----
From: "Ismael González" <[email protected]>
To: "B2G Dev List" <[email protected]>
Sent: Thursday, August 22, 2013 2:48:24 AM
Subject: [b2g] -moz-apperance input radio/checkbox
Hi all,
I'm Ismael González <basiclines> and i am currently working with Arnau <rnowm> and
Pavel Ivanov <pivanov> in the Building Blocks refactor.
I wanted to raise up an issue that has been there since many time, at least 3
years, and it's about you can't style a radio/checkbox input via CSS due to
heavy binding to UA styles:
https://bugzilla.mozilla.org/show_bug.cgi?id=605985
The goal is allow to style them via `-moz-appearance: none` as it already
happen in other browser engines.
This will allow us (Building Blocks project) to simplify the markup for our
custom radio/check/switch elements that currently relays on `input:checked +
span` rules.
As this components are being used among all the Gaia project, i think the
benefits are obvious.
Thx
BTW: web developers community will love to have this fixed also in Firefox :D
--Ismael González / @basiclines
_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g
_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g
