- From: <bugzilla@jessica.w3.org>
- Date: Fri, 12 Jun 2015 08:30:56 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28775 Michael Kay <mike@saxonica.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WONTFIX --- Comment #3 from Michael Kay <mike@saxonica.com> --- Response on behalf of the Working Group: Many thanks for reviewing the specification and making this suggestion. While WG members agreed that this change would be beneficial for the use cases described, there were two concerns: (a) there is a balance to be found between making the implicit priority rules more intelligent, and keeping them memorable. There are limits to our ability to "do the right thing" in all cases for users who don't use any user-defined priority attributes and rely on the system to take care of it. On the whole, we would encourage people with complex sets of template rules to be aware of priorities and set them manually where necessary (or even where not necessary). (b) any change to the default priority rules for constructs that were legal in XSLT 2.0 will break existing code, and we don't make breaking changes unless there are very strong justifications indeed; the case here is not strong enough. We hope you will accept this decision by marking the bug as closed, but if you want to reopen the discussion with new information you are welcome to do so. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Friday, 12 June 2015 08:31:00 UTC