1165312 - TEST-FAIL | suite/browser/test/browser/browser_bug581947.js | setCustomValidity should exist for keygen

Status: RESOLVED WORKSFORME

(SeaMonkey :: Testing Infrastructure, defect)

Description

[Ian Neal]

Running browser_bug581947.js fails with the following error:
TEST-FAIL | suite/browser/test/browser/browser_bug581947.js | setCustomValidity should exist for keygen

Comment 1

[Philip Chee]

Mounir Lamouri wrote the original Firefox test

(In reply to Ian Neal from comment #0)
> Running browser_bug581947.js fails with the following error:
> TEST-FAIL | suite/browser/test/browser/browser_bug581947.js |
> setCustomValidity should exist for keygen

Any idea why this test is failing in SeaMonkey?

Comment 2

[Ian Neal]

(In reply to Philip Chee from comment #1)
> Mounir Lamouri wrote the original Firefox test
> 
> (In reply to Ian Neal from comment #0)
> > Running browser_bug581947.js fails with the following error:
> > TEST-FAIL | suite/browser/test/browser/browser_bug581947.js |
> > setCustomValidity should exist for keygen
> 
> Any idea why this test is failing in SeaMonkey?

It is an expected FAIL on both Firefox and SeaMonkey, so perhaps it is due to be fixed?

Comment 3

[Mounir Lamouri (:mounir)]

Yeah, it's an expected failure. It seems to be the same as https://dxr.mozilla.org/mozilla-central/source/testing/web-platform/meta/html/dom/interfaces.html.ini

Are SeaMonkey bots ignoring the expected failure or is it passing on SeaMonkey?

Comment 4

[Jonathan Kingston [:jkt] he/him]

Bug 1315460 resolved this by removing support completely to match the web standard and also Chrome.