Re: [w3c/uievents] Consider splitting the spec into smaller specifications (Issue #369)

@LJWatson : Considering the state of the specs and the amount of work needed, I believe that we won't be able to get UI Events to REC **unless** we split it up. Splitting out Keyboard `code` and `key` values into separate documents is the only reason why we were able to move those forward. We also need to convert the spec to be algorithmic, and that will be much easier if we can attack the problem piecemeal.

@patrickhlauke : One of the motivations for the monolithic spec was that there were interdependencies and event timing concerns that were easier to manage in a single document. PE (correctly, IMO) decided it was better to be a separate spec because they wanted to be able to actually finish the work without being anchored to all the other bits in UIEvents. Of course, that leads to interdependencies between the specs. Splitting up UI Events will cause more of these hooks/links between the specs, but it's a problem that needed to be solved in any case.

@smaug---- : I think that would be good outcome. And if the HTML spec is not sufficient, then it might make sense to update it rather than create a new FocusEvents spec.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/uievents/issues/369#issuecomment-1918064586
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/uievents/issues/369/1918064586@github.com>