934115 - m.9292.nl website displays two arrows in a drop down menu

Status: RESOLVED INVALID

(Firefox OS Graveyard :: Gaia::Browser, defect)

Description

[Alexander van Loon]

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 (Beta/Release)
Build ID: 20130917102605

Steps to reproduce:

I visited the http://m.9292.nl/ website with the Firefox OS browser .


Actual results:

You can see two arrows in the drop down menu with the date (the website is in Dutch, but it's hard to miss). The website has its own arrow for the drop down menu, but if viewed in Firefox there is an extra arrow all the way to the right.


Expected results:

Firefox shouldn't display that extra arrow. My first thought was that the website's designers were at fault, but the website displays correctly in a WebKit-based browser such as GNOME Web 3.8.2. This is why I think the problem lies in Firefox. I will add screenshots to demonstrate this. The screenshot of Firefox rendering the website was made with the non-mobile Linux version of Firefox, but the rendering is identical.

Comment 1

[Alexander van Loon]

Attachment: A screenshot of Firefox 24.0 rendering m.9292.nl

Comment 2

[Alexander van Loon]

Attachment: A screenshot of GNOME Web 3.8.2 rendering m.9292.nl

Comment 3

[Alexander van Loon]

Attachment: A screenshot of GNOME Web 3.8.2 rendering m.9292.nl

Apparently made a mistake in adding the last attachment, fixed now.

Comment 4

[Jan Jongboom [:janjongboom] (inactive)]

This is a bug in the 9292 mobile website.

.text-field select {width:100%;height:36px;-moz-box-sizing:border-box;-ms-box-sizing:border-box;-webkit-box-sizing:border-box;box-sizing:border-box;float:none;-webkit-appearance:none}

They're specifying -webkit-appearance, but not -moz-appearance. Not that moz-appearance is flawless (https://gist.github.com/joaocunha/6273016), but there is bug 649849 for that.

Comment 5

[Alexander van Loon]

I just mentioned this bugreport in a message I sent to 9292.nl, strangely they say they don't reply to comments about their website (!), but let's hope they will fix it.

But what I don't understand is why they should specify the appearence for different web browser rendering engines? I thought the whole idea of standards like HTML5 is that we (especially Mozilla) aim to eliminate these browser-specific options so that website displays in an identical manner on different browsers?

Comment 6

[Jan Jongboom [:janjongboom] (inactive)]

Sure, but appearance is a non-standard feature at this moment (see https://developer.mozilla.org/en-US/docs/Web/CSS/-moz-appearance). That means that implementations between browsers will differ; and that's why it's behind a prefix at this moment. If there is a standard the prefixes will be dropped.