RE: [ff-dev] CSS performance

[Kugelman, J. <jku...@pr...>]

Without actually having thought about the CSS problem in detail, my hope
is that we will only have to implement the parsing end of it and leave
the rendering, cascading, etc. to the browsers.

For example, add classes to each element like .first-child,
.enabled/.disabled, .required/.optional, and so on. Then we can have the
CSS parser translate pseudo-classes into real classes. We could have it
translate pseudo-elements into real elements.

This is just my hope, though. Whether or not this approach will work for
all other CSS3 constructs, I do not know.

John
=20
> -----Original Message-----
> From: for...@li...
[mailto:formfaces-
> dev...@li...] On Behalf Of Micah Dubinko
> Sent: Thursday, May 05, 2005 6:57 PM
> To: Stefano Debenedetti
> Cc: for...@li...
> Subject: [ff-dev] CSS performance
>=20
> On the topic of CSS performance, Dave Hyatt of Apple Safari has some
> interesting comments:
>=20
> http://weblogs.mozillazine.org/hyatt/archives/2005_05.html#007507
>=20
> -m
>=20
> --
>   Available for consulting. XForms, web forms, information overload.
>   Micah Dubinko                           mailto:mi...@du...
>   Brain Attic, L.L.C.                        http://brainattic.info
>   Yahoo IM: mdubinko                                +1 623 298 5172
>   Learn XForms today: http://xformsinstitute.com
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.Net email is sponsored by: NEC IT Guy Games.
> Get your fingers limbered up and give it your best shot. 4 great
events, 4
> opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
> win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=3D20
> _______________________________________________
> FormFaces-development mailing list
> For...@li...
> https://lists.sourceforge.net/lists/listinfo/formfaces-development