What I miss from Web Components currently: * ability to change inside styles from the outside, but not in a hacky way, more using exposed CSS API using CSS pseudo elements. I know this is being discussed currently but I really hope we'll be able to have this soon. * and... that's actually all ;)
We also have this issue that can bite us: https://bugzilla.mozilla.org/show_bug.cgi?id=1208113 Note sure how our colleagues in the Music app managed to avoid it :) Le 28/10/2015 09:33, Wilfred Mathanaraj a écrit : > Hi all > > In the past we had a proposal to use web-components to bring > uniformity to the UX on FxOS - we did a partial implementation of this > and it has left our UX with an “unfinished” look and feel. > Moving forward we want to have a very uniform UX across all our core > apps. We also want to make this uniform experience available to > contributors. > > Having common components to achieve this will also help with the > following: > > 1. UX to easily manage UX changes > 2. Engineering to reduce code size by using these common components > 3. QA to reduce their testing > > One of the methods we identified is web-components and there have been > some concerns raised with : > > 1. time taken to implement each component > 2. possible performance impacts web-components calls may have. > > We are currently trying to identify other possibilities to achieve > such a uniform implementation - if any of you have any proposals > please feel free to reach out to Rob, Hema, or myself. > > BR > Wilfred > > > > --- > FxOS Product Management > Mozilla Corp., UK > > > > > > > _______________________________________________ > dev-fxos mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-fxos
signature.asc
Description: OpenPGP digital signature
_______________________________________________ dev-fxos mailing list [email protected] https://lists.mozilla.org/listinfo/dev-fxos
