- From: <bugzilla@jessica.w3.org>
- Date: Thu, 12 May 2016 13:16:07 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29492 --- Comment #2 from Abel Braaksma <abel.braaksma@xs4all.nl> --- > This drops the current possibility for an attribute-set to be consuming. I > think that's probably a useful simplification, Agreed. There's a myriad of other ways to achieve this. Furthermore, this simplifies overriding as a processor will know beforehand that an attribute set is never going to consume and can inline the code without worrying about streamability issues. > I don't think they should have a usage, but if any, the usage is inspection and > have themselves no additional operands, as they are not allowed to "absorb" any > node. My stance is now that they can be removed from the operands (perhaps with a Note), or alternatively, as we do with some other non-relevant (i.e., always grounded) operands, add a note that this or that is the operand usage and role, but that it does not influence the analysis. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Thursday, 12 May 2016 13:16:11 UTC