Re: Why is text crossed out in implementation guide?

I haven't had time to make a general announcement of the changes I made
to the checkin I did last night.

Any substantial content edits, I did with <ins> and <del> markup to
facilitate review. I didn't do a lot of content editing, but there were
cases where I really felt things were unclear, and the edits are
attempts to make things more clear.

In the case you reference, the removed text is replaced by inserted text
a little bit lower that says normalize the whitespace, including
trimming any spaces you've added. I find that more clear and believe it
doesn't change the meaning, but if you disagree with that, let me know.

Almost always, deleted text is accompanied by inserted text nearby, so
please review deletions and insertions together. The default stying in
my user agent is to render inserted text as underline and deleted text
as strikeout.

Michael

Aaron M Leventhal wrote:
>
> Hi Michael,
>
> "Prepend a space if necessary: if the current node is an element and
> is not styled with display: inline, append a space character if the
> text equivalent result string is not currently empty. This space
> character should be removed at the end, if the entire text equivalent
> computation for an element yields no other results. "
>
> and
>
> "Append a space if necessary: if the current node is an element and is
> not styled with display: inline, append a space character. This last
> space should be trimmed off if it ends up being last character in the
> entire text equivalent computation for an element. "
>
> Why are the second sentences crossed out? It's necessary to do those
> steps so that truly empty names show as being empty.
>
> - Aaron 

-- 

Michael Cooper
Web Accessibility Specialist
World Wide Web Consortium, Web Accessibility Initiative
E-mail cooper@w3.org <mailto:cooper@w3.org>
Information Page <http://www.w3.org/People/cooper/>