-
Notifications
You must be signed in to change notification settings - Fork 4
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
query parameter to show position regions #409
Comments
@terracoda please review by adding It looks like: |
Looks good. This should work for me. Just one fix... I think "at middle" is a single value region, so the line should probably go through the middle of the words like "at top" and "at bottom". |
I'll assign back as soon as I determine the new region ranges. |
Oh no! I just realized that I input the incorrect values for the ranges, I used the distance ranges instead of the position ones. One fix coming in up. |
@terracoda I'm so terribly sorry for wasting your time. Please re-review. |
From the screenshot it does not look like "at middle" or "at top" are single-value regions. |
Ok, I think you got the original PDOM regions now! That's nice! I am wondering for Voicing if we can change the ranges for the 3 main regions around the middle to eliminate the dashed regions, "in upper-middle region" and "in lower-middle" region. I worked the following regions out in a table in the design doc: |
I am wondering for Voicing if we can change the ranges for the 3 main regions around the middle to eliminate the dashed regions, "in upper-middle region" and "in lower-middle" region. Over in #433 it is very unclear if we are actually going to go through with this work. If we do, it will happen in that issue, and we can consider how it will effect this query parameter there. I did rename it to After #437 this is what the position regions layer now looks like: @terracoda, is there anything else for this issue? |
I don't think so. I don't think we will change the regions after all, except the change we already made around the middle, ... and now that I re-look at my table, I think I may have been trying to address that edge case with the simplified regions. Anyways, changing the regions the least amount as possible is good in the long run. |
Closing. |
Like we did in GFL and BASE
This is just the general regions when there are no tick marks.
The text was updated successfully, but these errors were encountered: