1379107 - Wifi purchase form onboard IcelandAir broken in Firefox Desktop

Status: RESOLVED DUPLICATE of bug 1373826

(Firefox :: Untriaged, defect)

Description

[Bogdan Surd, QA [:bsurd, NI]]

Attachment: icelandair-wifi-purchase.zip

Environment:
OS: 
 - Windows 10 Creators Update
Build: 
 - 54.0.1

Created from Bug 1373826 Comment 7
----------------------------------
STR in Bug 1373826 Comment 5
> It's possible to partially reproduce the issue with regular Firefox for
> Desktop, too, if you resize the window to make it very narrow, so that only
> the left 2 CC number fields are visible.
> 
> After you enter 0000 0000 0000 0000
> the left hand side of the credit card form is scrolled out.
> 
> There isn't any visible mechanism to scroll to the left.
> 
> On Desktop Firefox this can be fixed by pressing the "tab" key. I don't know
> if I could have used a tab key on the Android keyboard, at least I didn't
> have that idea.

Comment 1

[:Gijs (he/him)]

Karl, can you take a look? Feels like a tech evangelism issue.

Comment 3

[u597127]

(In reply to :Gijs (no reviews, mostly out until Jul 17) from comment #1)
> Karl, can you take a look? Feels like a tech evangelism issue.

Why do you think it isn't a rendering bug in Firefox?

And wouldn't it have made more sense to keep the original bug report as the primary bug, and just change the component of the original bug? It has much more information.

Comment 4

[:Gijs (he/him)]

(In reply to honigfalle from comment #3)
> (In reply to :Gijs (no reviews, mostly out until Jul 17) from comment #1)
> > Karl, can you take a look? Feels like a tech evangelism issue.
> 
> Why do you think it isn't a rendering bug in Firefox?

I don't know that it is or isn't, someone would need to take a look, for which I don't have time. The bug got filed in a component I try to help triage, which is why I touched it, but I normally work on Firefox frontend issues and am very busy (and also, currently, on holiday). The web compat / tech evangelism folks are the most experienced in doing further triage. However, given the description of what's happening in comment 0, and what I've seen of bugs concerning specific websites filed in bugzilla without a description of *why* something is a Firefox issue (other than "it works in Chrome" which is not especially indicative considering how many pages do browser sniffing these days), my bet is on a website issue. I assume the website sets overflow: hidden somewhere it shouldn't. We won't know for sure until someone analyzes this bug and creates a minimal testcase.

> And wouldn't it have made more sense to keep the original bug report as the
> primary bug, and just change the component of the original bug? It has much
> more information.

I didn't dupe the bug. Forwarding this question to Wesly, because I don't know - if this is a gecko (ie firefox rendering) issue then the fix will almost certainly affect both desktop and mobile, and I'm not entirely sure why we needed a separate bug filed to begin with...

Comment 5

[Thomas Wisniewski]

Based on the zip attachment, this is fixed by the instruction bug 1088586 comment 3 (adding min-width:0 to the flexed input elements). But Chrome apparently fixed the bug that caused the compat issue in bug 1088586, so I'm not 100% sure which rendering is correct here. I'm going to add dholbert to this discussion to get some more insight.

Comment 6

[Daniel Holbert [:dholbert]]

Agreed, we should've just reclassified the original bug (and generally when we dupe, it's better to dupe newer/less-info bugs to older/more-info bugs).

Let's reverse the dupe relationship & take the discussion back over to the original bug.  I'll post a comment there with more diagnosis on the layout problem in a bit.

Comment 7

[Wesly Huang (EPM)]

Sorry for setting the confusing bug dependency, and thanks for the help!