[Bug 26424] Tag omission rules for rp could break invalid-but-existing content

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26424

--- Comment #6 from Koji Ishii <kojiishi@gluesoft.co.jp> ---
(In reply to Koji Ishii from comment #5)
> After looking at this test results, I started to wonder, maybe this isn't as
> critical as I originally thought.

I mean, changing rp not to auto-close anything will actually fix pages with rp
inside rt.

See the test results at
http://www.browserstack.com/screenshots/68cc77ec6804d2a6bbc7de29f55f99a14744977d
Browsers that render rp inside rt as ruby are: IE 6/7/8/9
Browsers that do not render rp inside rt as ruby are: IE 10/11, Chrome 35,
Safari 7
Firefox not included in the above list because it does not render ruby anyway.

So, the changing will:
* Fix web pages written for IE 6/7/8/9 (real sites wchen found are probably in
this category)
* Break web pages that rely on auto-closing behavior of rp for IE 10-, Chrome,
Safari

But as long as rp inside rt is already broken, I can't think of single example
where rp not auto-closing anything will break.

So, unless I miss something, I think compatibility concern is a needless fear,
we can safely fix rp not to auto-close anything.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Monday, 28 July 2014 19:18:12 UTC