Closed Bug 35652 Opened 25 years ago Closed 25 years ago

<strike> doesn't render as striked

Categories

(Core :: Layout, defect, P2)

PowerPC
Mac System 8.5
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: Brade, Assigned: dcone)

Details

(Keywords: platform-parity)

This is a mac-specific bug (apparently works on Windows; not sure about linux). HTML which contains <strike> doesn't render with a line through the text. To reproduce, create an html file in the editor and apply strikethrough (Format -> Text Style) and then save the file and preview it in browser. Expected: should render strikethrough in both editor and browser Simon adds this comment: "I think it's calling FillRect with a zero-height rect"
Keywords: pp
Priority: P3 → P2
I made an HTML file, and put a <s> this is Strike </s> and a <strike> this is Strike </strike> Both worked great... Had a fresh pull as of 4/18/2000.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
reopening since I still see this with today's build. Note, in my case the file is a minimal file produced from Composer.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
I had the QA person test this.. and it also worked for him. We made a sample in the Editor, composer, and Dreamweaver. Checked this with todays build on my machine,, and his machine and they all worked. I don't know what to do. I will give this to you.. maybee you can come up with a test case, something that can show this bug.
Assignee: dcone → brade
Status: REOPENED → NEW
Assignee: brade → dcone
ok; I tracked this down (I think). I see this problem because my default font size isn't the 16 that we ship as default but rather 12 point (variable width font in the browser). Reassign back to dcone
It was a problem with getting the height of the strike linewidth. The width was being rounded.. and then converted.. and it was ending up 0 width. I rounded the number properly.. and it works now.
Status: NEW → RESOLVED
Closed: 25 years ago25 years ago
Resolution: --- → FIXED
Kathy, I not reproducing this problem in the May 22 Mac build. Could you please verify this too ?
This problem is fixed in the May 29th build. Marking verified.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.