Closed Bug 296937 Opened 20 years ago Closed 18 years ago

long ACRONYM title is clipped without human-sense = clipped by pixel borders

Categories

(Core :: Layout, defect)

x86
Windows XP
defect
Not set
trivial

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: tachyon.eagle, Unassigned)

References

()

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050606 Firefox/1.0+ Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050606 Firefox/1.0+ I've just added several <acronym title="..."> into my pages, and I have found out that if the title content is too long, browser will clip it, fine..., but it adds three dots at the end , so if the content is exactly 1 character above limit, it's cut and three dots are displayed instead of it . I have found out that Mozilla / Firefox (latest snapshots) define the border exactly with pixels, not characters. But for human-beings, I think that displaying "91%" is better than "91..." , even if that dotted may be 1 pixel shorter .... It may also be same for <abbr> tag, but such a long content si not probable within it's title. Reproducible: Always Steps to Reproduce: 1. make acronym title long just to be clipped from last character Actual Results: last character is clipped and three dots are displayed instead of it Expected Results: displayed the last character,even if it have to enlarge border area a few pixels , or clip more reasonably , the last word or more characters for example
Wouldn't a fix to bug 45375 be a better solution, aka, _the_ solution?
Depends on: 45375
wfm Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8.0.7) Gecko/20060829 Firefox/1.5.0.7 wfm Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8.1) Gecko/20060922 BonEcho/2.0 wfm Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8.1) Gecko/20060919 SeaMonkey/1.1b tested on testcase http://desitka.sh.cvut.cz/~quentar/testacr.htm Feel free to reopen if bug still seen on trunk
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.