- From: <bugzilla@jessica.w3.org>
- Date: Mon, 03 Oct 2011 18:52:55 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14360
Ian 'Hixie' Hickson <ian@hixie.ch> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ian@hixie.ch
Component|LC1 HTML5 spec (editor: Ian |HTML5 spec (editor: Ian
|Hickson) |Hickson)
--- Comment #6 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-10-03 18:52:55 UTC ---
(In reply to comment #0)
>
> PROBLEM DESCRIPTION: Bug 13502 resulted in a de-facto permisson to let text
> runs begin with combining marks. However, while it should perhaps not be
> completely forbidden, still - if an element "whose content model allows any
> flow content" contains nothing but (inter-element) space + combining mark (or
> even solely a combining mark), then there are several potential issues:
>
> 1) White space collapsing means that the combining character doesn't really
> combine with the space character
Why would this be a problem?
> 2) Combing marks that combines with nothing or space, are hard to select with
> the mouse
Why would they be any harder than combining with a letter?
> 3) Visually, such marks may look as if they combine with something outside the
> element
They might well combine with something outside the element's border box. Why is
this a problem?
> 4) When the first letter is a combnining mark, then the CSS *:first-letter{}
> selector may seem, to authors, to not work
Why not? It would do exactly what CSS says it should, no?
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Monday, 3 October 2011 18:52:57 UTC