- From: <bugzilla@jessica.w3.org>
- Date: Tue, 26 Feb 2013 21:10:22 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19858 --- Comment #4 from Tim Mills <tim@cbcl.co.uk> --- Further investigation shows that the specification makes provision for a processor to disable a feature which it supports in response to a prohibit-feature declaration, but there is no corresponding provision for a processor to enable a feature in response to a require-feature declaration which it supports but which is not enabled by default. I will raise this as a separate bug. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 26 February 2013 21:10:24 UTC