This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Core test domconfigparameternames01 checks canSetParameter functionality by going through the list of parameters obtained from calling getParameterNames. However, the DOMStringList of parameterNames "can also contain parameter names defined outside this specification." [1] Thus in this test, canSetParameter is called on some parameters not recognized in the method (certain parameters are defined outside of the spec) and a FEATURE_NOT_FOUND error is raised. Test should be modified to call canSetParameter and setParameter only after asserting that parameter name is one recognized in the spec. [1]http://www.w3.org/TR/2004/REC-DOM-Level-3-Core- 20040407/core.html#DOMConfiguration-parameterNames
I believe the test reflects the wording and intent of the spec and that the proposed change is not appropriate. Unless you want to withdraw it, it will need to go to the IG for resolution. parameterNames of type DOMStringList, readonly The list of the parameters supported by this DOMConfiguration object and for which at least one value can be set by the application. Note that this list can also contain parameter names defined outside this specification. canSetParameter name does not declare that NOT_FOUND_ERR can be raised and does not restrict applicability to only parameters defined in the spec. "for which at least one value can be set" indicates that a NOT_FOUND_ERR would be inappropriate for setParameter(parameter[i], someval), if there was any problem it would be in the value and should result in a NOT_SUPPORTED_ERR or TYPE_MISMATCH_ERR. Since the parameter can be set to a value, then the operation of retrieving a value should not throw a NOT_FOUND_ERR.