cc @whsieh @rniwa @mustaq @gked
I'm not sure where you prefer the issues to be filed. Against the explainer here or against the spec under Ryosuke's repo. Maybe if we just create one repo in WICG for this it might be more visible and clear for the folks. Feel free to contact one of the WICG owners (like @yoavweiss) for moving this under WICG. Anyhow, I'm filing one here and we can move the discussion anywhere we like later.
Following the comment from @johanneswilm comment during the breakout session that the rich editors are not going to give up their own undo manager stack (for different reasons like collaborative history effect that will always be there) and may be only using this API for the last two items, I was wondering whether we can start off with something like that.
Basically I wonder what happens if we remove the nested undo managers as well as letting the app to add/modify/see the whole list. What happens if we just expose that last undo/redo item and let the app set those. This would solve all those already existing rich editors as well as exposing setting the label or any other platform ui/text for those actions if available on the platform. Also per another comment in the session when changing language they don't need to go and change the whole list. But they just need update the single item for redo/undo with the new language maybe.
Obviously I haven't thought the format of such API but if we go with that we should definitely have it in a way that can be extended to what the current proposal exposes (mainly the nesting functionality and full history). So we can extend it when there is enough need for these extension.
I wonder what other's thoughts are about this.
cc @whsieh @rniwa @mustaq @gked
I'm not sure where you prefer the issues to be filed. Against the explainer here or against the spec under Ryosuke's repo. Maybe if we just create one repo in WICG for this it might be more visible and clear for the folks. Feel free to contact one of the WICG owners (like @yoavweiss) for moving this under WICG. Anyhow, I'm filing one here and we can move the discussion anywhere we like later.
Following the comment from @johanneswilm comment during the breakout session that the rich editors are not going to give up their own undo manager stack (for different reasons like collaborative history effect that will always be there) and may be only using this API for the last two items, I was wondering whether we can start off with something like that.
Basically I wonder what happens if we remove the nested undo managers as well as letting the app to add/modify/see the whole list. What happens if we just expose that last undo/redo item and let the app set those. This would solve all those already existing rich editors as well as exposing setting the label or any other platform ui/text for those actions if available on the platform. Also per another comment in the session when changing language they don't need to go and change the whole list. But they just need update the single item for redo/undo with the new language maybe.
Obviously I haven't thought the format of such API but if we go with that we should definitely have it in a way that can be extended to what the current proposal exposes (mainly the nesting functionality and full history). So we can extend it when there is enough need for these extension.
I wonder what other's thoughts are about this.