jal.co.jp - double dropdown arrows on SELECT-elements

[hallvors]

URL: https://sp5971.jal.co.jp/sp/RsvFlightInfo.do Browser / Version: Firefox Mobile 38.0 Operating System: Android Problem type: Something else - I'll add details below

Steps to Reproduce 1) Navigate to: https://sp5971.jal.co.jp/sp/RsvFlightInfo.do (this is a step in the booking process for national flights - if you can't go there directly, start at jal.co.jp, tap national (map of Japan+plane icon), tap first option. 2) Double down-arrows are rendered on some SELECT elements

[hallvors]

Compatipede says:

"-webkit-appearance used without equivalents for .btnR in https://sp5971.jal.co.jp/mobiled/dom/css/rsv.css:291:104, value: none",
"-webkit-appearance used without equivalents for .btnGSub in https://sp5971.jal.co.jp/mobiled/dom/css/rsv.css:329:107, value: none",

It's probably the correct analysis for this problem. We now need to find a contact at JAL.

[miketaylr]

So this is kind of weird, from https://sp5971.jal.co.jp/mobiled/dom/css/dom_module.css.

div.domModule table td select {
    font-weight: bold;
    font-size: 18px;
    height: 54px;
    border: medium none;
    border-radius: 0px;
    background-color: transparent;
    background-position: 97% 50%;
    width: 100%;
    -moz-appearance: treeitem;
}

If you change -moz-appearance to none, we lose the extra dropdown arrow (since Bug 649849

[kudodo]

Mozilla Japan has contact, will contact them.

[kudodo]

I've send a message from Web form today.

[kudodo]

The response is that "Standard browser of each device are supported, therefore Firefox is not supported for the mobile site. However JAL understands that the importance of OS and browser diversity." They will share our request in the team. Looking forward to hearing from them!

[karlcow]

To note that the full CSS for these buttons is

div.domModule table td select {
    font-weight: bold;
    font-size: 18px;
    height: 54px;
    border: none;
    border-radius: 0px;
    -webkit-border-radius: 0px;
    background-color: transparent;
    background-position: 97% 50%;
    width: 100%;
    -webkit-appearance: button;
    -moz-appearance: treeitem;
    appearance: button;
    background-image: url(/common/img/bg_dom_select_arw.png);
    background-repeat: no-repeat;
    background-size: 14px 14px;
    -webkit-background-size: 14px 14px;
}

Wondering if appearance: button should generate the same behavior in WebKit, Blink and Gecko

[karlcow]

@kudodo without insisting too much. because they already put in there

div.domModule table td select {
  …
   -moz-appearance: treeitem;
  …
}

to

div.domModule table td select {
  …
   -moz-appearance: none;
  …
}

and we would be good.

[karlcow]

What it looks like in Firefox Android with layout.css.prefixes.webkit;false

And in Blink.

switching to layout.css.prefixes.webkit;true does NOT solve anything. There are issues for example with the tree widgets for selection.

[karlcow]

@kudodo any news from JAL. Given it's only changing one value in the property they already have in their CSS targeting moz.

[karlcow]

Contacted them through https://rgst.jal.co.jp/cgi-bin/jal/goiken/goiken.cgi?phase=1&e=1

[karlcow]

JAL answer

Please be informed that we are now taking your proposal under consideration among concerned divisions. We will reply to you as soon as all the results are confirmed.

[karlcow]

JAL's answer on 2016-09-05

Dear Mr. Dubost,

We appreciate your patience as we took the　time to carefully review the matters.

As we are planning a large system renovation, we regret that we are not able to cope with this case at present. It may take time, but we are still investigating where we can deal with it. As soon as the investigation is completed we will contact you again.

While we feel sorry that we not able to reply positively, your kind understanding toward our current situation is much appreciated.

We thank you once again for your kind proposal.

Sincerely yours,

[MDTsai]

This URL works for me as Chrome's screenshot in https://github.com/webcompat/web-bugs/issues/1005#issuecomment-181240909

@karlcow I guess we can close this as fixed?

[karlcow]

yup. They changed the design.