Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Focus needs to be discussed in depth along with the model for how multiple EditContext objects can be associated with a document #8

Open
BoCupp-Microsoft opened this issue Nov 12, 2018 · 3 comments

Comments

@BoCupp-Microsoft
Copy link

No description provided.

@ssanupam24
Copy link

Should focus be tightly coupled with SIP? or do we need a separate API to set SIP display policy (manual/automatic)?

@dlibby-
Copy link
Owner

dlibby- commented Nov 30, 2018

Leaving this open for now, will sync up on thinking here

@dlibby-
Copy link
Owner

dlibby- commented Nov 30, 2018

After further discussion, we're going to have a complimentary focus model, where the focus/active element and tab indexing won't change, key events will still be sent to the focused element, but editing events will be dispatched on the EditContext. I'll need to explain these sequences of events, including composition

gked pushed a commit to gked/EditContext that referenced this issue Apr 22, 2019
Update expainer.md - address issues 4 and 5
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants