Bug 1756203 Comment 16 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

I think I'm mostly-done expressing my own opinions for now (hopefully I've made my concerns/thoughts/edge-cases-to-consider fairly clear), and I'm curious to hear what thoughts mozilla's a11y folks & frontend designers might have on this.

Also: given that the current behavior seems to be interoperable across all browsers, it feels like maybe this proposal is something that we'd need to discuss with other browsers in a standards-body and get feedback from other browsers & standardize on a solution for this.

(And if the standardized behavior ends up being "yes, just please treat all of this content as part-of-the-web-page and scale it with full-page zoom" which seems to be the request here, then so be it & we can go from there.  Or if the outcome is "Browsers should provide users with a minimum-font-size-for-browser-UI including UI that shows up in-content" or something else completely different, then we can go from there.  But it would be not-great to have full-page zoom scaling different and potentially non-overlapping sets of things in different browsers, and I want to be sure we don't end up there.)
I think I'm mostly-done expressing my own opinions for now (hopefully I've made my concerns/thoughts/edge-cases-to-consider fairly clear), and I'm curious to hear what thoughts mozilla's a11y folks & frontend designers might have on this.

Also: given that the current behavior seems to be interoperable across all browsers, it feels like maybe the resulting proposal here might be something that we'd need/want to discuss with other browsers in a standards-body and get feedback from other browsers & standardize on a solution for this.

(And if the standardized behavior ends up being "yes, just please treat all of this content as part-of-the-web-page and scale it with full-page zoom" which seems to be the request here, then so be it & we can go from there.  Or if the outcome is "Browsers should provide users with a minimum-font-size-for-browser-UI including UI that shows up in-content" or something else completely different, then we can go from there.  But it would be not-great to have full-page zoom scaling different and potentially non-overlapping sets of things in different browsers, and I want to be sure we don't end up there.)
I think I'm mostly-done expressing my own opinions for now (hopefully I've made my concerns/thoughts/edge-cases-to-consider fairly clear), and I'm curious to hear what thoughts mozilla's a11y folks & frontend designers might have on this.

Also: given that the current behavior seems to be interoperable across all browsers, it feels like maybe the resulting proposal here might be something that we'd need/want to discuss with other browsers in a standards-body and get feedback from other browsers & standardize on a solution for this.

(And if the standardized behavior ends up being "yes, just please treat all of this content as part-of-the-web-page and scale it with full-page zoom" which seems to be the request here, then so be it & we can go from there.  Or if the outcome is "Browsers should provide users with an option to configure minimum-font-size-for-browser-UI including UI that shows up in-content" or something else completely different, then we can go from there.  But it would be not-great to end up with "full-page zoom" being a feature that scales different and potentially non-overlapping sets of things in different browsers, and I want to be sure we don't end up there.)
I think I'm mostly-done expressing my own opinions for now (hopefully I've made my concerns/thoughts/edge-cases-to-consider fairly clear), and I'm curious to hear what thoughts mozilla's a11y folks & frontend designers might have on this.

Also: given that the current behavior seems to be interoperable across all browsers, it feels like maybe the resulting proposal here might be something that we'd need/want to discuss with other browsers in a standards-body and get feedback from other browsers & standardize on a solution for this.

(And if the standardized behavior ends up being "yes, just please treat all of this content as part-of-the-web-page and scale it with full-page zoom" which seems to be the request here, then so be it & we can go from there.  Or if the outcome is "Browsers should provide users with an option to configure minimum-font-size-for-browser-UI including UI that shows up in-content" or something else completely different, then we can go from there.  But it would be not-great to end up with "full-page zoom" being a feature that scales different and potentially non-overlapping sets of things in different browsers, and I want to avoid inadvertently ending up there if we and other browsers were do address this sort of issue in different patchwork-style ways.)
I think I'm mostly-done expressing my own opinions for now (hopefully I've made my concerns/thoughts/edge-cases-to-consider fairly clear), and I'm curious to hear what thoughts mozilla's a11y folks & frontend designers might have on this.

Also: given that the current behavior seems to be interoperable across all browsers, it feels like maybe the resulting proposal here might be something that we'd need/want to discuss with other browsers in a standards-body and get feedback from other browsers & standardize on a solution for this.

(And if the standardized behavior ends up being "yes, just please treat all of this content as part-of-the-web-page and scale it with full-page zoom" which seems to be the request here, then so be it & we can go from there.  Or if the outcome is "Browsers should provide users with an option to configure minimum-font-size-for-browser-UI including UI that shows up in-content" or something else completely different, then we can go from there.  But it would be not-great to end up with "full-page zoom" being a feature that scales different and potentially non-overlapping sets of things in different browsers, and I want to avoid inadvertently ending up there, if we and other browsers were to address this sort of issue in different patchwork-style ways.)

Back to Bug 1756203 Comment 16