Bug 322616 - Support ruby annotation in the HTML and JSP Design pages
Summary: Support ruby annotation in the HTML and JSP Design pages
Status: NEW
Alias: None
Product: Java Server Faces
Classification: WebTools
Component: UI (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: Future   Edit
Assignee: JSF Project UI CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks: 241276
  Show dependency tree
 
Reported: 2010-08-12 23:11 EDT by Jesse Viviano CLA
Modified: 2013-11-19 14:55 EST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jesse Viviano CLA 2010-08-12 23:11:26 EDT
Build Identifier: 20100617-1415

Note: this has nothing to do with the Ruby programming language, but a somewhat recent addition to XHTML and HTML called ruby markup.

The design page in the HTML and the JSP editors cannot support ruby annotation, which is defined in http://www.w3.org/TR/2001/REC-ruby-20010531/ and incorporated into XHTML 1.1 as shown in http://www.w3.org/TR/xhtml11/doctype.html . An article about ruby markup can be found at http://en.wikipedia.org/wiki/Ruby_character . Since ruby markup is one of the major changes made to create XHTML 1.1 from XHTML 1.0 Strict and was added to HTML in the creation of HTML5, Eclipse WTP cannot support XHTML 1.1, XHTML5, or XHTML5 correctly until ruby support is added.

Reproducible: Always

Steps to Reproduce:
1.Create an XHTML 1.1, XHTML 5, or an HTML5 document. Earlier versions of XHTML and HTML do not support ruby markup.
2.Choose either page display with the design page and the source page. These views are indicated with buttons on the top of Eclipse with dark green and dark cyan rectangles.
3.Enter some text with ruby markup into the source page.
3.In the design page, the ruby is misrendered like in browsers without ruby support.
Comment 1 Nick Sandonato CLA 2011-11-09 17:59:15 EST
Hi Jesse,

I know it's been awhile, but I assume this defect is about rendering ruby in the Web Page Editor. Is that correct? If it's about supporting the actual content model, we have an enhancement open already under Bug 262398.
Comment 2 Nick Sandonato CLA 2013-11-19 14:21:06 EST
Since it appears this is in regards to the design pane in the Web Page Editor, I'm reassigning the enhancement.