Splitting proposals

[foolip]

In #190 we identified that a number of proposals already have comments suggesting splitting:

• Clipboard API #143
• Other Embedded Content #147
• Machine Learning in the Browser #152
• History and navigation, including the Navigation API #170
• Web Components #181
• PWA manifest and push notifications #218

It's up to the person who proposed to decide if they want to split it, but here's a tracking issue with checklists so that we can follow up on that.

[gsnedders]

It's up to the person who proposed to decide if they want to split it

Or to someone else to file a counter-proposal which is a subset of the original one.

[bkardell]

As said on the call today - I feel like we need more advice in how to split it up, more advice on why/how we'd like to split would be helpful I guess. MathML, for example, is new in chromium but a mature feature in other browsers (and beyond) - however MathML-Core which does all of the actual platform integration (except parsing which has been normalized since hixie) is kind of new to all of them. Aligning DOM stuff from SVG and MathML is new, but really pothole filling stuff we've been doing (like, the fact that you didn't have a .style property on these was weird, for example). "Too big" or "Too broad" is fine, I expect that most people (like me) are very willing to split it up, it just would be real helpful to have some better advice on how to do that - what are we looking for.

[gsnedders]

#181 seems to be the only one still needing split at this point; it seems like #143 and #152 don't need split (albeit the descriptions perhaps changed?). Are we still going to accept a split, even after the deadline for proposals has past?

[foolip]

Closing as we're passed the deadline to refine proposals now.