1578631 - vertical alignment of inline images

Status: RESOLVED DUPLICATE of bug 1570096

(Core :: Layout: Images, Video, and HTML Frames, defect)

Description

[shige]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36 Edge/15.15063

Steps to reproduce:

accessed normaly the web page, especially made by latex2html.

Actual results:

If two or more inline images are in a text line with specifications of vertical alignment, current version of firefox make incorrect view.
This feature may have been changed at some version of firefox, in fact,
the view on firefox is different with it on waterfox, and I remember old firefox
made correct view.
This change makes bad view for the page made by latex2html which is LaTeX
to HTML translator. It uses vertical alignments of inline images for good viewing.

test page: http://takeno.iee.niit.ac.jp/%7Eshige/TeX/latex2html/test-va/test-va.html
(vertical alignment test page for small, middle, big images)

Expected results:

I think vertical alignment of current firefox is not correct, and behaviors of old
firefox and waterfox (and Opera, Chrome, Safari, MS-IE) are correct.

Comment 1

[shige]

Attachment: test-va-firefox.pdf

screenshot of test-va.html by firefox.

Comment 2

[shige]

Attachment: test-va-waterfox.pdf

screenshot of test-va.html by waterfox.

Comment 3

[shige]

Attachment: test-va-opera.pdf

screenshot of test-va.html by opera.

Comment 4

[shige]

Add attachment files of screenshots for above test page by firefox, waterfox, and opera.
The view of opera is ther same as of waterfox, but firefox is not.
Well, I think not all the waterfox's view are correct. The "top" alignments seem to use "line-top", not "text-top".
Firefox seems to use always "line-top" and "line-bottom" instead of "text-top" and "text-bottom".

Comment 5

[Liviu Seplecan]

Attachment: bug - 1578631 - Chrome.png

Comment 6

[Liviu Seplecan]

Attachment: bug - 1578631 Firefox.png

Comment 7

[Liviu Seplecan]

Hi @shige, confuse description..... I will send you how looks on my end on Chrome & FF. Please describe with accurate info what is the issue....for example...in your screenshots appears to be in print preview mode....nothing specified in the description about that..
Regards,
Liviu

Comment 8

[shige]

Attachment: test-va3-firefox.pdf

screenshot of test-va3 by firefox.

Comment 9

[shige]

Attachment: test-va3-waterfox.pdf

screenshot of test-va3 by waterfox

Comment 10

[shige]

Thank you for your reply. Our chrome's feature is the same as yours. But, firefox's is not the same. Please see test-va-firefox.pdf.
On firefox, small image with "Bottom" alignment appears too low position. The bottom position of the small image is the same as the bottom position of large image. On chrome, the bottom position of the small image is the bottom of text line, not the bottom of large image.

Latex2html uses bottom and middle alignment to inline images for justified them to text line. For example, I attached screenshots
by firefox and waterfox to the small sample of latex2html:
http://takeno.iee.niit.ac.jp/~shige/TeX/latex2html/test-va/test-va3/index.html
Waterfox is good, but firefox is not. Chrome, opera and safari may display correctly.

I think the newer version of latex2html should write out CSS style vertlical-align instead of align property of image tag, and it will be displayed
correctly even on firefox. But firefox cannot display current contents translated by latex2html correctly at present.

Comment 11

[Liviu Seplecan]

Attachment: both screenshots aren't necessarily

Comment 12

[Liviu Seplecan]

Hi @shige, verifying all tree FF versions: nightly 71.0a1, beta 70.0b4 ( the issue won't occur), only on release 69.0 the issue can be reproduced. Please grab the nightly & beta versions then re-test the issue and tell me the results: link for nightly ( https://nightly.mozilla.org/ ) / link for beta (https://www.mozilla.org/en-US/firefox/channel/desktop/)
Addittionally, I run a mozregression & here are the results:
first bad:
build_date: 2019-06-16
changeset: 19cf79b6f07d4c5c93d29d6b73d40df4497db657
pushlog_url: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=11b4d70a2b5d6373f5ec8fa01ca48a1c7bc1829e&tochange=19cf79b6f07d4c5c93d29d6b73d40df4497db657

last good:
build_date: 2019-05-01 17:06:38.844000
changeset: e4210db75a7f22d639f59fe5955de6bf62582df9
pushlog_url: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=e4210db75a7f22d639f59fe5955de6bf62582df9&tochange=c7a22f0ea7b4ce3ff379f5be1d1ad3070aa76317

2019-09-10T11:21:00: DEBUG : Found commit message:
Backed out changeset 8c89fd37b79d (bug 1544242) for failures in browser_rules_shadowdom_slot_rules.js CLOSED TREE

Since the issue won't occur in nightly & beta maybe someone from dev team could give us a hand with the fix on release.
Regards,
Liviu

Comment 13

[Emilio Cobos Álvarez [:emilio]]

Yes, I accidentally broke it in 69, it's fixed in 70 (bug 1570096).