* SUMMARY When ruby support is disabled (by turning off ENABLE_RUBY) in WebKit with a pre-HTML5 parser, fallback rendering of ruby content fails because the ruby tags are not completely ignored (as they were before ruby support was added). * STEPS TO REPRODUCE 1. Launch Safari with ENABLE_RUBY turned off. 2. Open test URL: <http://www.yomiuri.co.jp/world/news/20101127-OYT1T00240.htm> * EXPECTED RESULTS The <ruby> and related tags should be ignored, and the ruby text should be rendered inline with the other text in the paragraph. * ACTUAL RESULTS The <ruby> tags appear to be parsed and rendered, but not in the correct location on the page (if ruby support was enabled). * REGRESSION This is a regression from before ruby support was added to WebKit. * NOTES This bug is only for historical purposes at this point. Bug 49272 removed the ENABLE_RUBY switch because ruby is a fully supported feature of HTML5 in WebKit. See also Bug 34698 (which was the last bug to add back the ENABLE_RUBY switch).
<rdar://problem/8706857>
> This bug is only for historical purposes Can this bug be closed as INVALID or WONTFIX? As it doesn't apply to WebKit ToT, I don't see any reason to keep it open. If not today, when can it be resolved?
(In reply to comment #2) > Can this bug be closed as INVALID or WONTFIX? As it doesn't apply to WebKit ToT, > I don't see any reason to keep it open. If not today, when can it be resolved? Technically, it's blocked on the invention of a time machine, but in lieu of that, I'll close it as RESOLVED/WONTFIX. :)