JDK-7071674 : Cannot use bidi in Swing html text
  • Type: Enhancement
  • Component: client-libs
  • Sub-Component: javax.swing
  • Affected Version: 7u2
  • Priority: P3
  • Status: Open
  • Resolution: Unresolved
  • OS: generic
  • CPU: generic
  • Submitted: 2011-07-27
  • Updated: 2018-09-05
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
tbdUnresolved
Related Reports
Relates :  
JDK-4296022 - html4.x support within a JEditorPane
Description
SYNOPSIS
--------
Cannot use bidi in Swing html text

OPERATING SYSTEM
----------------
All

FULL JDK VERSION
----------------
All

PROBLEM DESCRIPTION from LICENSEE
---------------------------------
It is currently impossible to use bidi html text in Swing components, due to the fact that the span tag and its "dir" attribute are not supported by the HTML parser built into the JDK.

We understand that this could be considered part of the the umbrella CR 4296022 (opened back in 1999), which deals with updating the HTML parser to comply with HTML 4.x, but we feel that this particular aspect deserves to be considered separately. Currently it is impossible for the whole of the Middle Eastern market to use HTML in Swing components. Implementing this specific part of the HTML 4.x specification would be a small amount of work compared to the activity requested under CR 4296022.

TESTCASE
--------
Attached

REPRODUCTION INSTRUCTIONS
-------------------------
Run the attached testcase and observe that it is impossible to set the direction of HTML text in swing components.
Comments
- this is an issue reported against 7(7u), - there are now affected version 9 filed for this issue - 7u issues are transferred to Sustaining Nevertheless if someone have a report against 9 - please reopen and add affectedVersion 9 or 7u specific escalations might be reopen to Sustaining
10-08-2014
- this is an issue reported against 7(7u), - there are now affected version 9 filed for this issue - 7u issues are transferred to Sustaining Nevertheless if someone have a report against 9 - please reopen and add affectedVersion 9 or 7u specific escalations might be reopen to Sustaining
10-08-2014