[Webkit-unassigned] [Bug 50247] New: Fallback rendering fails when ruby support is disabled (with pre-HTML5-parser)

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Nov 30 10:26:21 PST 2010


https://bugs.webkit.org/show_bug.cgi?id=50247

           Summary: Fallback rendering fails when ruby support is disabled
                    (with pre-HTML5-parser)
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Macintosh
               URL: http://www.yomiuri.co.jp/world/news/20101127-OYT1T0024
                    0.htm
        OS/Version: Mac OS X 10.6
            Status: NEW
          Keywords: NeedsReduction, Regression
          Severity: Normal
          Priority: P2
         Component: Layout and Rendering
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: ddkilzer at webkit.org
                CC: mjs at apple.com, adele at apple.com


* 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).

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the webkit-unassigned mailing list