8924 - Font tag does not have an effect when using the iso-8859-6 character set (Arabic)

Status: VERIFIED INVALID

(Core :: CSS Parsing and Computation, defect, P3)

Description

[waseem]

I am currently running Arabic Windows 98 and using build no 1999062113, if you
go to http://www.sayegh.com/test1_iso.htm (a test page for the iso-8859-6
character set) you will find that the <Font> tag does not change the color or
size of the font. You can only see this bug if you are looking at Arabic
characters. As if you look at the same exact page with Latin characters then
there won't be a problem. The same page was viewed with IE 4 with Arabic
support and nothing was wrong with it.

Comment 1

[Peter Linss]

Pushing off non-beta 1 issues

Comment 2

[Pierre Saslawsky]

Reassigning peterl's bugs to myself.

Comment 3

[Pierre Saslawsky]

Accepting peterl's bugs that have a Target Milestone

Comment 4

[Pierre Saslawsky]

Pushing my M15 bugs to M16

Comment 5

[Pierre Saslawsky]

Cowardly reassigning i18n/style issues to attinasi. On my list, they are likely 
to stay buried for a very long time.

Comment 6

[Marc Attinasi]

I marked this as dependent on 28500: when we correctly deal with unicode style 
sheets and declarations this should be fixed.

Comment 7

[Marc Attinasi]

I believe my recent changes to support the @charset directive in stylesheets, 
and related changes to use the charset of the document for inline style, should 
fix this. I cannot test it, however, as I do not have Arabic Windows. If anybody 
wants to help test I'd be happy to send out the changes, just ask.

Comment 8

[Marc Attinasi]

I have checked in changes to support other charsets; can somebody test this and 
see if it is fixed as well? I will try and find the font being used and test it 
on my English Windows system in the meantime.

Comment 9

[Marc Attinasi]

I do not have Arabic Windows, but I downloaded the Arabic fonts and installed 
them and the test page does render in what I believe to be Arabic characters, 
however assertions abound about illegal characters in buffer routines. One thing 
I noticed is that there seems to be an error in the FONT tage's color value: it 
should have a '#' in front of the hex values:

  <FONT color=fff566 size=5> should be 
  <FONT color=#fff566 size=5>

That appears to be the cause of at least some of the assertions.

I'm still hoping to get somebody else's verification on this bug...

Comment 10

[Marc Attinasi]

The FONT tag has an invalid color (needs a # before the hex value). This is 
causing the color to be ignored.

I have solicited help on fixing this testcase so I can test to see if the bug 
still exists, however I have received no response. When I force the browser to 
interpret the color anyway (in the debugger) the color or the character is 
yellow, which appears to be correct.

Marking INVALID since the testcase is invalid. Please reopen with a valid 
testcase if there is still a bug here. 

Comment 11

[Christine Hoffman]

Verifying invalid per comments.

Comment 12

[Shmuel Popper]

M16 does display the character in yellow (win2000 with Arabic installed).