Re: interact-pevents-04-t

Hi Erik.

Erik Dahlstrom:
> There is one more interesting item on the list:
> -------------8<--------
> Q. Does that mean that a font can never display one of these characters?
> A: No. Rendering systems may also support special modes such as
> “Display Hidden”, which are intended to reveal characters that would
> not otherwise display. Fonts can contain glyphs intended for visible
> display of default ignorable code points that would otherwise be
> rendered invisibly when not supported.
> -------------->8------------

That is an interesting find.

> That says that it's alright to have glyphs for "invisible"
> characters intended for use when an application enables a special
> mode to show control characters so it's not totally meaningless
> (though not very meaningful in most cases).
> Any objections to me making an imagepatch to remove the visible
> spaces in the reference image and tweaking the test description to
> make that clear?

I made a small test to see whether a space glyph is rendered in HTML
content (using a WOFF and TTF font):

It seems that in IE9, Firefox and WebKit, the U+0020 glyph is rendered,
and I would like the handling of white space glyphs to be the same in
HTML and SVG content.  I’d like to see what the CSS Working Group’s
opinion on this is.  Could you mail www-style about it?

In any case, I think there is sufficient doubt surrounding the rendering
of white space glyphs to avoid having it in the test (for now, at
least).  I would be fine with removing the sub-test that checks for the
rendering of those glyphs and moving it to a new, unapproved test.  Do
you know if any other tests in the test suite rely on the rendering of
white space glyphs?  (I feel like there are some.)

Cameron McCormack ≝

Received on Tuesday, 4 January 2011 21:56:48 UTC