Updates:
Owner: ---
Comment #6 on issue 1069 by mikesamuel: runtime fontFamily assignment
throws error
http://code.google.com/p/google-caja/issues/detail?id=1069
We cannot do that because the set of words that may have other
meanings is potentially infinite given possible future extensions.
Possible future browser extensions or caja extensions?
Possible future CSS and browser extensions.
We could quote unquoted names before passing them through, which is what
the server side CSS rewriter does.
I assume you mean passing them through to the browser's native behavior.
I'm not sure I understand the difference between passing through the
unquoted name with the quoted name.
FF, Saf, Op, & IE honor el.style.fontFamily = '"serif"' e.g.
Yes.
Well, the CSS spec (
http://www.w3.org/TR/css3-fonts/#font-family-the-font-family-property ) says
The name can optionally be enclosed in quotes. This also allows
for referencing faces that belong to larger families that cannot
otherwise be referenced.
which means that
font-family: serif
means use a serif font, while
font-family: "serif"
means use the font named "serif."
At any rate, if this will remove the potential of throwing a runtime
error in response to a fontFamily assignment, I'm all for it.
As to why stacks aren't allowed, that is probably a bug.
Should I file a separate bug for that or is it alright to address that
from this bug?
I think it's fine as is.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
