Bug 802882 (html5test)

Improve score on html5test.com

NEW
Unassigned

Status

()

Core
General
5 years ago
22 hours ago

People

(Reporter: dbaron, Unassigned)

Tracking

(Depends on: 35 bugs, Blocks: 1 bug, {meta})

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

Attachments

(1 attachment)

(Reporter)

Description

5 years ago
This bug exists to track things we can do to improve our score on http://html5test.com/ , the source of which exists at https://github.com/NielsLeenheer/html5test/ .

While presence in this test doesn't necessarily change the priority of our work, it is interesting enough to track.
(Reporter)

Updated

5 years ago
Depends on: 629350, 799318, 748351
(Reporter)

Updated

5 years ago
Depends on: 601912
(Reporter)

Updated

5 years ago
Depends on: 33339, 676619, 629801, 591737
(Reporter)

Updated

5 years ago
Depends on: 746087
(Reporter)

Updated

5 years ago
Depends on: 773205, 344618, 547004, 101019, 723008
(Reporter)

Updated

5 years ago
Depends on: 341604, 80713, 508725
(Reporter)

Updated

5 years ago
Depends on: 779297, 643325
(Reporter)

Updated

5 years ago
Depends on: 670898
(Reporter)

Updated

5 years ago
Depends on: 556743, 675943
(Reporter)

Updated

5 years ago
Depends on: 631218
No longer depends on: 80713
(Reporter)

Updated

5 years ago
Depends on: 802895
(Reporter)

Updated

5 years ago
Depends on: 782211
(Reporter)

Comment 1

5 years ago
https://github.com/NielsLeenheer/html5test/pull/211
(Reporter)

Comment 2

5 years ago
And the most useful view of this bug is probably:
https://bugzilla.mozilla.org/showdependencytree.cgi?id=802882&maxdepth=1
Depends on: 760140
(Reporter)

Updated

5 years ago
Depends on: 749459, 559284, 562008

Comment 3

5 years ago
This should also depends on bug #344614.
(Reporter)

Comment 4

5 years ago
(In reply to Fabio from comment #3)
> This should also depends on bug #344614.

I think it already has all the individual dependencies marked, so we don't also need to depend on the meta-bug for HTML5 forms (which depends on other things that aren't relevant to html5test.com).

Comment 5

5 years ago
(In reply to David Baron [:dbaron] from comment #4)
> (In reply to Fabio from comment #3)
> > This should also depends on bug #344614.
> 
> I think it already has all the individual dependencies marked, so we don't
> also need to depend on the meta-bug for HTML5 forms (which depends on other
> things that aren't relevant to html5test.com).

At least 446510 is still missing.
(Reporter)

Comment 6

5 years ago
I had bug 773205 instead, but that indeed looks like a duplicate of bug 446510.
Depends on: 446510
No longer depends on: 773205
Depends on: 825294

Comment 7

5 years ago
Files bug #828974 which is related to this tracking bug.
Depends on: 828974

Updated

4 years ago
Depends on: 833385
Depends on: 891287
Depends on: 702870
No longer depends on: 891287
There's a new version coming (http://beta.html5test.com/) that adds many new tests like WebRTC and WebGL2.
I don't know how to add dependencies with this new Bugzilla interface, these are the ones I found for the new version of the test:
Bug #493857 (Security/CSP)
Bug #600919 (2D/WebP)
Bug #750010 (P2P/WebRTC on Android)
Bug #778617 (Video/Media Source extensions)
Bug #833023 (Video/VP9 Support)
Bug #878828 (Input/Gamepad)
Bug #889977 (3D/WebGL 2)
Bug #910138 (2D/Ellipse)
Bug #923590 (Video/DRM Support (not!) )

I couldn't found bugs for Audio/Speech Recognition, Video/Codec Detection, 2D/Path, 2D/Dashed Line, 2D/Hit Testing, 2D/High Resolution, Security/Web and Cryptography API.

Comment 10

4 years ago
You may not have the permissions to make these changes. You only can add dependencies while you create a new one.
May be it make sense to create a separated tracking bug for the new test?

Comment 11

4 years ago
(In reply to sjw from comment #10)
> May be it make sense to create a separated tracking bug for the new test?

No real need for a new tracking but since beta.html5test.com will become html5test.com

Comment 12

4 years ago
2D/High resolution as currently tested is going away, so no bug needed here: http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2013-September/040735.html

Bug filed: https://github.com/NielsLeenheer/html5test/issues/286

Comment 13

4 years ago
The developer just confirmed [1] that DRM support does not change the score, so Bug 923590 (and related) should not be tracked by this bug. If this ever changes in the future, we can add it back. 

[1] https://github.com/NielsLeenheer/html5test/issues/287

Comment 14

4 years ago
Canvas Path is Bug 830734. Dashed support is Bug 768067 (and/or one of the bugs I mentioned in Bug 768067 Comment 7). 

I linked some discussions about the features here: https://github.com/NielsLeenheer/html5test/issues/287#issuecomment-26158091 – so there may be changes coming up. I voted for not counting these, too, which would make the bugs uninteresting for this bug.
Depends on: 830734, 768067, 665909, 750011

Comment 15

4 years ago
(In reply to Alexandre Folle de Menezes from comment #9)
> I couldn't found bugs for […] Video/Codec Detection

That's Bug 884275. Please add as dependancy.


Enough bugspam for now, sorry!

Updated

4 years ago
No longer depends on: 923590
Depends on: 884275

Comment 16

4 years ago
Often at beta.html5test.com I get the Javascript message "Test has failed: Permission denied to access property 'encrypt'" and no score. Usually takes several page refreshs until everything works fine.

I observed this with versions 24.0 up to 27.0, all on Linux64 (though not necessarily limited to Linux64). This doesn't seem to occur with other browsers though, so I assume it's some imperfect feature implementation in Firefox, which I don't know.

Comment 17

4 years ago
(In reply to Markus Popp from comment #16)
> Often at beta.html5test.com I get the Javascript message "Test has failed:
> Permission denied to access property 'encrypt'" and no score. Usually takes
> several page refreshs until everything works fine.
> 
> I observed this with versions 24.0 up to 27.0, all on Linux64 (though not
> necessarily limited to Linux64). This doesn't seem to occur with other
> browsers though, so I assume it's some imperfect feature implementation in
> Firefox, which I don't know.

It's filled as: https://bugzilla.mozilla.org/show_bug.cgi?id=927901

Comment 18

4 years ago
Per https://github.com/NielsLeenheer/html5test/issues/297, moar dependancies (this is not yet visible on the test page).
Depends on: 897102
Tom's Hardware Guide's "Web Browser Grand Prix" (tracking bug 933949) includes html5test.
Blocks: 933949
No longer blocks: 933949
Blocks: 933949

Updated

4 years ago
Depends on: 822898

Comment 23

4 years ago
How about #693083 and #966591?

Comment 24

4 years ago
Bug 693083 / CSS Selectors Lvl 4 is not tested by HTML5Test.
Depends on: 966591

Updated

3 years ago
Depends on: 888320

Comment 25

3 years ago
I've set up Win 8.1 x64 Enterprise Eval as a VM with VMWare and installer Firefox Aurora and later Firefox Beta to see, how the results on html5test.com will improve in a future version.
However: The result is actually 447 points in both, which is 1 point less, than the current release version. Can anybody tell me, what went wrong?

UA: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:29.0) Gecko/20100101 Firefox/29.0
Christian: the html5test results page shows a break down of the individual features, so you should be able find the regression by comparing the subsections' points.

On OS X, however, I don't see a regression:

* Firefox 28 = 448
* Firefox Beta 29 = 467
* Firefox Aurora 30 = 467
* Firefox Nightly 31 = 475
* Chrome 34 = 505

Comment 27

3 years ago
(In reply to Chris Peterson (:cpeterson) from comment #26)
> * Firefox Nightly 31 = 475
> * Chrome 34 = 505

Are there plans to implement the missing form input types, especially the date/time types, any time soon? That should lift Firefox's score up to about where Chrome is now.
(In reply to Christian Stadler from comment #25)
> I've set up Win 8.1 x64 Enterprise Eval as a VM with VMWare and installer
> Firefox Aurora and later Firefox Beta to see, how the results on
> html5test.com will improve in a future version.
> However: The result is actually 447 points in both, which is 1 point less,
> than the current release version. Can anybody tell me, what went wrong?

Are you sure you have the latest versions installed? My results on Win7 (32-bit):

Firefox 28 = 444
Firefox Beta 29 = 463
Firefox Aurora 30 (2014-04-22) = 463
Firefox Nightly 31 (2014-04-22) = 475

(In reply to Markus Popp from comment #27)
> (In reply to Chris Peterson (:cpeterson) from comment #26)
> > * Firefox Nightly 31 = 475
> > * Chrome 34 = 505
> 
> Are there plans to implement the missing form input types, especially the
> date/time types, any time soon? That should lift Firefox's score up to about
> where Chrome is now.

You may want to follow bug 888320 and related ones. Though from having a look at their history it doesn't seem there was big progress on them lately.

Sebastian

Comment 29

3 years ago
(In reply to Chris Peterson (:cpeterson) from comment #26)
> Christian: the html5test results page shows a break down of the individual
> features, so you should be able find the regression by comparing the
> subsections' points.
> 
> On OS X, however, I don't see a regression:
> 
> * Firefox 28 = 448
> * Firefox Beta 29 = 467
> * Firefox Aurora 30 = 467
> * Firefox Nightly 31 = 475
> * Chrome 34 = 505

The problem was, that firefox seems to blacklist the VMWare video driver by default.
Setting webgl.force-enabled to true in about:config fixed the issue with WebGL being disabled. Now I've got 467 points on Beta 29 and Aurora 30

See also: https://support.mozilla.org/de/questions/865633

Comment 30

3 years ago
html5test on Firefox for Android says input type=[month, week, datetime] are not supported even if they are supported. Is this an issue on their testing method, or anything missing on the Firefox for Android side?

Comment 31

3 years ago
(In reply to merihakar from comment #30)
> html5test on Firefox for Android says input type=[month, week, datetime] are
> not supported even if they are supported. Is this an issue on their testing
> method, or anything missing on the Firefox for Android side?

This should pass on Android. Which version were you testing with? Can you test again with a currently Nightly, please?

Comment 32

3 years ago
(In reply to Florian Bender from comment #31)
> (In reply to merihakar from comment #30)
> > html5test on Firefox for Android says input type=[month, week, datetime] are
> > not supported even if they are supported. Is this an issue on their testing
> > method, or anything missing on the Firefox for Android side?
> 
> This should pass on Android. Which version were you testing with? Can you
> test again with a currently Nightly, please?

It's the same in today's Nightly, see http://img.mpopp.net/fx32html5test.png

Comment 33

3 years ago
What's your result on http://modernizr.github.io/Modernizr/test/index.html, inputtypes section?

Comment 34

3 years ago
Oh, and what inputs don't work here: https://miketaylr.com/pres/html5/forms2.html

Comment 35

3 years ago
Created attachment 8416420 [details]
modernizr input tests in Firefox for Android 29

On modernizr test page only date and time input types passes the test (see screenshot).

All date/time inputs work properly on https://miketaylr.com/pres/html5/forms2.html

Comment 36

3 years ago
Please file a bug then so we can investigate this further: How do the tests determine support, and why do they fail on Android? I don't have an Android device so I can't really help there. Thanks.

Comment 37

3 years ago
Look at the code sample, this is extracted from how html5test.com verifies support for input elements (month in this example):

http://jsfiddle.net/mpopp75/YWwC6/

For some reason, on Firefox Android the element.field.type value is not month (as in this example) as one would expect.

Comment 38

3 years ago
Filed bug #1005268

Updated

3 years ago
Depends on: 1005268
Depends on: 1003439

Updated

2 years ago
Depends on: 1157724

Updated

2 years ago
Depends on: 840640
Depends on: 1059784
Component: Tracking → DOM: Core & HTML
(Reporter)

Updated

a year ago
Component: DOM: Core & HTML → General

Updated

9 months ago
Depends on: 1185106

Updated

9 months ago
Depends on: 568953

Updated

9 months ago
Depends on: 1128959

Updated

4 months ago
See Also: → bug 913153
Summary: improve score on html5test.com → Improve score on html5test.com
This issue is about improving the score, but some of the issues added recently do not impact the score:

    [Bug 500500] Add support for JPEG-XR/HD Photo
    [Bug 577084] Implement HTTP Live Streaming (HLS) for audio and video on Android
    [Bug 1263150] Adding native support for MPEG-DASH
    [Bug 1294490] Implement experimental WebP image support

Comment 40

a month ago
The "About HTML5test" section of the test implies that all tested features can reward points so maybe this is just a bug. I have send an email to them to get clear of this.
No longer depends on: 856375
Depends on: 968586
You need to log in before you can comment on or make changes to this bug.