Closed
Bug 960888
Opened 11 years ago
Closed 5 years ago
Add some reftests asserting that <keygen> renders like <select> (and accepts CSS styling)
Categories
(Core :: Layout: Form Controls, enhancement)
Core
Layout: Form Controls
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: dholbert, Assigned: jkt)
References
Details
We currently have zero reftests with the <keygen> element. We should add some, to be sure we don't accidentally regress it.
Bug 101019 comment 45 has some example situations to test.
The reftests should just match a <keygen> in the testcase up against a <select> in the reference case.
(We can either (a) hardcode the <keygen>'s textual options into the <select> in the reference case, or (b) make the text transparent and specify a fixed size on the element, so that the exact text doesn't matter. Option (b) is probably preferable, so we don't have to update these reference cases every time the <keygen> options change.)
Updated•11 years ago
|
Severity: normal → enhancement
Comment 1•9 years ago
|
||
You may have already hit such a regression, as <keygen> may be converted to <select> when being parsed from string:
var element = document.createElement('keygen');
console.log("created", element.nodeName); // "KEYGEN"
var container = document.createElement('div');
container.innerHTML = '<keygen>';
console.log("container created", container.firstElementChild.nodeName); // "SELECT"
(Firefox 39.0.3 OSX)
Assignee | ||
Comment 2•5 years ago
|
||
Bug 1315460 resolved this by removing support completely to match the web standard and also Chrome.
Assignee: nobody → jkt
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•