Page MenuHomePhabricator

Problem with external link arrow in rtl languages
Closed, DeclinedPublic

Description

Author: wiki.pedia

Description:
There is a problem with the arrow which appears with a link to an external web page.
When the text wraps, the arrow appears in the wrong place, overlaying the text.

See, for example,

http://yi.wikipedia.org/wiki/%D7%B0%D7%99%D7%A7%D7%99%D7%A4%D6%BC%D7%A2%D7%93%D7%99%D7%A2:%D7%A0%D7%99%D7%A6%D7%9C%D7%A2%D7%9B%D7%A7%D7%99%D7%99%D7%98%D6%BE%D7%90%D7%99%D7%A0%D7%99%D7%A6%D7%99%D7%90%D7%98%D7%99%D7%95%D7%95/%D7%A0%D7%99%D7%99%D7%A2_%D7%90%D7%99%D7%99%D7%92%D7%A0%D7%A7%D7%99%D7%99%D7%98%D7%9F


Version: unspecified
Severity: normal
URL: https://bugs.webkit.org/show_bug.cgi?id=9272

Details

Reference
bz24204

Event Timeline

bzimport raised the priority of this task from to Low.Nov 21 2014, 11:09 PM
bzimport set Reference to bz24204.
bzimport added a subscriber: Unknown Object (MLST).

wiki.pedia wrote:

Change the width of the the window so that the text wraps.

Which browsers + versions are you encountering this problem with ?

Not seeing it, even with a narrower window, on Firefox 3.6. I need specific browser information to be able to debug this.

wiki.pedia wrote:

Sorry, I forgot to check it with Firefox. FF 3.6 handles this OK.
But Safari, Chrome and Opera all overlay the arrow when the link text is wrapped.

I can confirm this behavior. Seems like a bug in Opera and Safari to me though....

Setting this to page rendering category (from i18n).

The report in comment 7 was a duplicate of https://bugs.webkit.org/show_bug.cgi?id=9272 (that issues does not appear to have gotten love since it was reported in June 2006).

Resolving later since this is an upstream bug that we have no control over.

Oh, looks like upstream has closed the dupe. Could someone verify that this is solved?

It works well on Google Chrome.

wiki.pedia wrote:

(In reply to comment #11)

It works well on Google Chrome.

Indeed it does.

But the problem remains on both Safari and Opera.

I tested this with Safari 5.1.2 and it works, so I am going mark this bug as WORKSFORME. Even if it is still a problem in Opera then it should not be labeled LATER because LATER suggests that we need to do something while this is obviously a browser issue.