A few additional thoughts/points that might clarify things here... (Kind of restating what I've said already, but perhaps in a clearer / more-structured way.) (1) Clearly Firefox itself (the application itself, menus, location bar, etc.) needs to have sufficiently-large-text to be readable to the user. Firefox defers to the system-default for text sizing here, I think; and the recommended way to customize this is to use the OS-specific system configuration tools to adjust resolution/application-text. (If those aren't sufficient for this purpose, then that'd be a legitimate issue that deserves its own bug.) (2) Web content **that is stylable by web developers** is in a different category and needs further intervention -- it cannot necessarily be assumed to be readable with the user's chosen OS settings, since web developers might e.g. specify too small of a font on a particular element, or make another inadvertently-bad design choice. Full-Page Zoom is one way of addressing this. (3) `<select>` dropdown menus fit into that second category -- the web developer has control over the font & font-size used in the `option` elements there, so they might be unreadably-small due to unfortunate choices on the part of the web developer. So, full-page-zoom applies to these dropdown menus, in order to give the user an option to mitigate one-off web developer design choices. (4) However, the other sorts of popups that I demonstrate in testcase 1 (including but not limited to `input` datalist-dropdowns) are simply part of the browser's own UI, and are **outside the control of web developers** and are the same size regardless of the website or of web developer choices. So I don't think it makes sense for full-page-zoom to apply to them -- if any of these pieces of UI have text that is too small, then that's either an indication that Firefox is failing to follow the system settings, or it's an indication that the system settings are misconfigured with smaller text (or finer resolution) than the user would actually prefer. In either case, I'd argue that broadening full-page-zoom would not be a robust fix, since the too-small UI here isn't website-specific; the best way to address this is to fix things (either at a system level or in Firefox, depending on the specifics) so that the relevant piece of Firefox's own UI is large enough for the user. Does this explanation make sense? And given the above, do you think there's actually a bug that needs fixing here, or is this just a case where you noticed the `<input>`-with-datalist dropdown behaving differently from `<select>` and thought that was unexpected? (As one "maybe-there's-no-bug" signal: on my system at least, the input-datalist dropdown text looks like it's the same size as the URLbar and tab-title text. If the former text is unreadably small, then I would expect the latter text to be unreadably small as well; and conversely, if users configure their system such that Firefox's tabs & URL bar are readable, then I would expect this would result in their input-datalist-dropdown text being readable as well.)
Bug 1756203 Comment 5 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
A few additional thoughts/points that might clarify things here... (Kind of restating what I've said already, but perhaps in a clearer / more-structured way.) (1) Clearly Firefox itself (the application itself, menus, location bar, etc.) needs to have sufficiently-large-text to be readable to the user. Firefox defers to the system-defaultsfor text sizing here, I think; and the recommended way to customize this is to use the OS-specific system configuration tools to adjust resolution/application-text. (If those aren't sufficient for this purpose, then that'd be a legitimate issue that deserves its own bug.) (2) Web content **that is stylable by web developers** is in a different category and needs further intervention -- it cannot necessarily be assumed to be readable with the user's chosen OS settings, since web developers might e.g. specify too small of a font on a particular element, or make another inadvertently-bad design choice. Full-Page Zoom is one way of addressing this. (3) `<select>` dropdown menus fit into that second category -- the web developer has control over the font & font-size used in the `option` elements there, so they might be unreadably-small due to unfortunate choices on the part of the web developer. So, full-page-zoom applies to these dropdown menus, in order to give the user an option to mitigate one-off web developer design choices. (4) However, the other sorts of popups that I demonstrate in testcase 1 (including but not limited to `input` datalist-dropdowns) are simply part of the browser's own UI, and are **outside the control of web developers** and are the same size regardless of the website or of web developer choices. So I don't think it makes sense for full-page-zoom to apply to them -- if any of these pieces of UI have text that is too small, then that's either an indication that Firefox is failing to follow the system settings, or it's an indication that the system settings are misconfigured with smaller text (or finer resolution) than the user would actually prefer. In either case, I'd argue that broadening full-page-zoom would not be a robust fix, since the too-small UI here isn't website-specific; the best way to address this is to fix things (either at a system level or in Firefox, depending on the specifics) so that the relevant piece of Firefox's own UI is large enough for the user. Does this explanation make sense? And given the above, do you think there's actually a bug that needs fixing here, or is this just a case where you noticed the `<input>`-with-datalist dropdown behaving differently from `<select>` and thought that was unexpected? (As one "maybe-there's-no-bug" signal: on my system at least, the input-datalist dropdown text looks like it's the same size as the URLbar and tab-title text. If the former text is unreadably small, then I would expect the latter text to be unreadably small as well; and conversely, if users configure their system such that Firefox's tabs & URL bar are readable, then I would expect this would result in their input-datalist-dropdown text being readable as well.)
A few additional thoughts/points that might clarify things here... (Kind of restating what I've said already, but perhaps in a clearer / more-structured way.) (1) Clearly Firefox itself (the application itself, menus, location bar, etc.) needs to have sufficiently-large-text to be readable to the user. Firefox defers to the system-defaultsfor text sizing here, I think; and the recommended way to customize its UI-text-size is to use the OS-specific system configuration tools to adjust resolution/application-text. (If those aren't sufficient for this purpose, then that'd be a legitimate issue that deserves its own bug.) (2) Web content **that is stylable by web developers** is in a different category and needs further intervention -- it cannot necessarily be assumed to be readable with the user's chosen OS settings, since web developers might e.g. specify too small of a font on a particular element, or make another inadvertently-bad design choice. Full-Page Zoom is one way of addressing this. (3) `<select>` dropdown menus fit into that second category -- the web developer has control over the font & font-size used in the `option` elements there, so they might be unreadably-small due to unfortunate choices on the part of the web developer. So, full-page-zoom applies to these dropdown menus, in order to give the user an option to mitigate one-off web developer design choices. (4) However, the other sorts of popups that I demonstrate in testcase 1 (including but not limited to `input` datalist-dropdowns) are simply part of the browser's own UI, and are **outside the control of web developers** and are the same size regardless of the website or of web developer choices. So I don't think it makes sense for full-page-zoom to apply to them -- if any of these pieces of UI have text that is too small, then that's either an indication that Firefox is failing to follow the system settings, or it's an indication that the system settings are misconfigured with smaller text (or finer resolution) than the user would actually prefer. In either case, I'd argue that broadening full-page-zoom would not be a robust fix, since the too-small UI here isn't website-specific; the best way to address this is to fix things (either at a system level or in Firefox, depending on the specifics) so that the relevant piece of Firefox's own UI is large enough for the user. Does this explanation make sense? And given the above, do you think there's actually a bug that needs fixing here, or is this just a case where you noticed the `<input>`-with-datalist dropdown behaving differently from `<select>` and thought that was unexpected? (As one "maybe-there's-no-bug" signal: on my system at least, the input-datalist dropdown text looks like it's the same size as the URLbar and tab-title text. If the former text is unreadably small, then I would expect the latter text to be unreadably small as well; and conversely, if users configure their system such that Firefox's tabs & URL bar are readable, then I would expect this would result in their input-datalist-dropdown text being readable as well.)
A few additional thoughts/points that might clarify things here... (Kind of restating what I've said already, but perhaps in a clearer / more-structured way.) (1) Clearly Firefox itself (the application itself, menus, location bar, etc.) needs to have sufficiently-large-text to be readable to the user. Firefox defers to the system-defaultsfor text sizing here, I think; and the recommended way to customize its UI-text-size is to use the OS-specific system configuration tools to adjust resolution/application-text. (If those aren't sufficient for this purpose, then that'd be a legitimate issue that deserves its own bug.) (2) Web content **that is stylable by web developers** is in a different category and needs further intervention -- it cannot necessarily be assumed to respect the user's chosen defaults, since web developers might e.g. specify too small of a font on a particular element, or make another inadvertently-bad design choice. Full-Page Zoom is one way of addressing this. (3) `<select>` dropdown menus fit into that second category -- the web developer has control over the font & font-size used in the `option` elements there, so they might be unreadably-small due to unfortunate choices on the part of the web developer. So, full-page-zoom applies to these dropdown menus, in order to give the user an option to mitigate one-off web developer design choices. (4) However, the other sorts of popups that I demonstrate in testcase 1 (including but not limited to `input` datalist-dropdowns) are simply part of the browser's own UI, and are **outside the control of web developers** and are the same size regardless of the website or of web developer choices. So I don't think it makes sense for full-page-zoom to apply to them -- if any of these pieces of UI have text that is too small, then that's either an indication that Firefox is failing to follow the system settings, or it's an indication that the system settings are misconfigured with smaller text (or finer resolution) than the user would actually prefer. In either case, I'd argue that broadening full-page-zoom would not be a robust fix, since the too-small UI here isn't website-specific; the best way to address this is to fix things (either at a system level or in Firefox, depending on the specifics) so that the relevant piece of Firefox's own UI is large enough for the user. Does this explanation make sense? And given the above, do you think there's actually a bug that needs fixing here, or is this just a case where you noticed the `<input>`-with-datalist dropdown behaving differently from `<select>` and thought that was unexpected? (As one "maybe-there's-no-bug" signal: on my system at least, the input-datalist dropdown text looks like it's the same size as the URLbar and tab-title text. If the former text is unreadably small, then I would expect the latter text to be unreadably small as well; and conversely, if users configure their system such that Firefox's tabs & URL bar are readable, then I would expect this would result in their input-datalist-dropdown text being readable as well.)
A few additional thoughts/points that might clarify things here... (Kind of restating what I've said already, but perhaps in a clearer / more-structured way.) (1) Clearly Firefox itself (the application itself, menus, location bar, etc.) needs to have sufficiently-large-text to be readable to the user. Firefox defers to the system-defaultsfor text sizing here, I think; and the recommended way to customize its UI-text-size is to use the OS-specific system configuration tools to adjust resolution/application-text. (If those aren't sufficient for this purpose, then that'd be a legitimate issue that deserves its own bug.) (2) Web content **that is stylable by web developers** is in a different category and needs further intervention -- it cannot necessarily be assumed to respect the user's chosen defaults, since web developers might e.g. specify too small of a font on a particular element, or make another inadvertently-bad design choice. Full-Page Zoom is one way of addressing this. (3) `<select>` dropdown menus fit into that second category -- the web developer has control over the font & font-size used in the `option` elements there, so they might be unreadably-small due to unfortunate choices on the part of the web developer. So, full-page-zoom applies to these dropdown menus, in order to give the user a tool to intervene and mitigate one-off web developer design choices. (4) However, the other sorts of dropdowns/popups that I demonstrate in testcase 1 (including but not limited to `input` datalist-dropdowns) are simply part of the browser's own UI, and are **outside the control of web developers** and are the same size regardless of the website or of web developer choices. So I don't think it makes sense for full-page-zoom to apply to them -- if any of these pieces of UI have text that is too small, then that's either an indication that Firefox is failing to follow the system settings, or it's an indication that the system settings are misconfigured with smaller text (or finer resolution) than the user would actually prefer. In either case, I'd argue that broadening full-page-zoom would not be a robust fix, since the too-small UI here isn't website-specific; the best way to address this is to fix things (either at a system level or in Firefox, depending on the specifics) so that the relevant piece of Firefox's own UI is large enough for the user. Does this explanation make sense? And given the above, do you think there's actually a bug that needs fixing here, or is this just a case where you noticed the `<input>`-with-datalist dropdown behaving differently from `<select>` and thought that was unexpected? (As one "maybe-there's-no-bug" signal: on my system at least, the input-datalist dropdown text looks like it's the same size as the URLbar and tab-title text. If the former text is unreadably small, then I would expect the latter text to be unreadably small as well; and conversely, if users configure their system such that Firefox's tabs & URL bar are readable, then I would expect this would result in their input-datalist-dropdown text being readable as well.)
A few additional thoughts/points that might clarify things here... (Kind of restating what I've said already, but perhaps in a clearer / more-structured way.) (1) Clearly Firefox itself (the application itself, menus, location bar, etc.) needs to have sufficiently-large-text to be readable to the user. Firefox defers to the system-defaultsfor text sizing here, I think; and the recommended way to customize its UI-text-size is to use the OS-specific system configuration tools to adjust resolution/application-text. (If those aren't sufficient for this purpose, then that'd be a legitimate issue that deserves its own bug.) (2) Web content **that is stylable by web developers** is in a different category and needs further intervention -- it cannot necessarily be assumed to respect the user's chosen defaults, since web developers might e.g. specify too small of a font on a particular element, or make another inadvertently-bad design choice. Full-Page Zoom is one way of addressing this. (3) `<select>` dropdown menus fit into that second category -- the web developer has control over the font & font-size used in the `option` elements there, so they might be unreadably-small due to unfortunate choices on the part of the web developer. So, full-page-zoom applies to these dropdown menus, in order to give the user a tool to intervene and mitigate one-off web developer design choices. (4) However, the other sorts of dropdowns/popups that I demonstrate in testcase 1 (including but not limited to `input` datalist-dropdowns) are simply part of the browser's own UI, and are **outside the control of web developers** and are the same size regardless of the website or of web developer choices. In other words, they're in the first category that I described above in point (1). I don't think it makes sense for full-page-zoom to apply to them -- if any of these pieces of UI have text that is too small, then that's either an indication that Firefox is failing to follow the user's preferences as expressed in the system settings, or it's an indication that the system settings need to be adjusted to match the user's preferences. In either case, I'd argue that broadening the applicability of full-page-zoom would not be a robust fix, since the too-small UI here isn't website-specific; the best way to address this is to fix things (either at a system level or in Firefox, depending on the specifics) so that the relevant piece of Firefox's own UI is large enough for the user. Does this explanation make sense? And given the above, do you think there's actually a bug that needs fixing here, or is this just a case where you noticed the `<input>`-with-datalist dropdown behaving differently from `<select>` and thought that was unexpected? (As one "maybe-there's-no-bug" signal: on my system at least, the input-datalist dropdown text looks like it's the same size as the URLbar and tab-title text. If the former text is unreadably small, then I would expect the latter text to be unreadably small as well; and conversely, if users configure their system such that Firefox's tabs & URL bar are readable, then I would expect this would result in their input-datalist-dropdown text being readable as well.)
A few additional thoughts/points that might clarify things here... (Kind of restating what I've said already, but perhaps in a clearer / more-structured way.) (1) Clearly Firefox itself (the application itself, menus, location bar, etc.) needs to have sufficiently-large-text to be readable to the user. Firefox defers to the system-defaultsfor text sizing here, I think; and the recommended way to customize its UI-text-size is to use the OS-specific system configuration tools to adjust resolution/application-text. (If those aren't sufficient for this purpose, then that'd be a legitimate issue that deserves its own bug.) (2) Web content **that is stylable by web developers** is in a different category and needs further intervention -- it cannot necessarily be assumed to respect the user's chosen defaults, since web developers might e.g. specify too small of a font on a particular element, or make another inadvertently-bad design choice. Full-Page Zoom is one way of addressing this. (3) `<select>` dropdown menus fit into that second category -- the web developer has control over the font & font-size used in the `option` elements there, so they might be unreadably-small due to unfortunate choices on the part of the web developer. So, full-page-zoom applies to these dropdown menus, in order to give the user a tool to intervene and mitigate one-off web developer design choices. (4) However, the other sorts of dropdowns/popups that I demonstrate in testcase 1 (including but not limited to `input` datalist-dropdowns) are simply part of the browser's own UI, and are **outside the control of web developers** and are the same size regardless of the website or of web developer choices. In other words, they're in the first category that I described above in point (1). I don't think it makes sense for full-page-zoom to apply to them -- if any of these pieces of UI have text that is too small, then that's either an indication that Firefox is failing to follow the user's preferences as expressed in the system settings, or it's an indication that the system settings need to be adjusted to match the user's preferences. In either case, I'd argue that broadening the applicability of full-page-zoom would not be a robust fix, since full-page-zoom is a website-specific intervention, and the styling/sizing of these popups is *not* website-specific. I'd think the best way to address this would be to do so at the root, i.e. to to fix things (either at a system level or in Firefox, depending on the specifics) so that the relevant piece of Firefox's own UI is actually large enough for the user to read. Does this explanation make sense? And given the above, do you think there's actually a bug that needs fixing here, or is this just a case where you noticed the `<input>`-with-datalist dropdown behaving differently from `<select>` and thought that was unexpected? (As one "maybe-there's-no-bug" signal: on my system at least, the input-datalist dropdown text looks like it's the same size as the URLbar and tab-title text. If the former text is unreadably small, then I would expect the latter text to be unreadably small as well; and conversely, if users configure their system such that Firefox's tabs & URL bar are readable, then I would expect this would result in their input-datalist-dropdown text being readable as well.)
A few additional thoughts/points that might clarify things here... (Kind of restating what I've said already, but perhaps in a clearer / more-structured way.) (1) Clearly Firefox itself (the application itself, menus, location bar, etc.) needs to have sufficiently-large-text to be readable to the user. Firefox defers to the system-defaultsfor text sizing here, I think; and the recommended way to customize its UI-text-size is to use the OS-specific system configuration tools to adjust resolution/application-text. (If those aren't sufficient for this purpose, then that'd be a legitimate issue that deserves its own bug.) (2) Web content **that is stylable by web developers** is in a different category and needs further intervention -- it cannot necessarily be assumed to respect the user's chosen defaults, since web developers might e.g. specify too small of a font on a particular element, or make another inadvertently-bad design choice. Full-Page Zoom is one way of addressing this. (3) `<select>` dropdown menus fit into that second category -- the web developer has control over the font & font-size used in the `option` elements there, so they might be unreadably-small due to unfortunate choices on the part of the web developer. So, full-page-zoom applies to these dropdown menus, in order to give the user a tool to intervene and mitigate one-off web developer design choices. (4) However, the other sorts of dropdowns/popups that I demonstrate in testcase 1 (including but not limited to `input` datalist-dropdowns) are simply part of the browser's own UI, and are **outside the control of web developers** and are the same size regardless of the website or of web developer choices. In other words, they're in the first category that I described above in point (1). I don't think it makes sense for full-page-zoom to apply to them -- if any of these pieces of UI have text that is too small, then that's either an indication that Firefox is failing to follow the user's preferences as expressed in the system settings, or it's an indication that the system settings need to be adjusted to match the user's preferences. In either case, I'd argue that broadening the applicability of full-page-zoom would not be a robust fix, since full-page-zoom is a website-specific intervention, and the styling/sizing of these popups is *not* website-specific. I'd think the best way to address this would be to do so at the root, i.e. to to fix things (either at a system level or in Firefox, depending on the specifics) so that the relevant piece of Firefox's own UI is actually large enough for the user to read. Does this explanation make sense? And given the above, do you think there's actually a bug that needs fixing here, or is this just a case where you noticed the `<input>`-with-datalist dropdown behaving differently from `<select>` and thought that was unexpected? (As one "maybe-there's-no-bug" signal: on my system at least, the input-datalist dropdown text looks like it's the same size as the URLbar and tab-title text. If the input-datalist dropdown text is unreadably small, then I would expect the URLbar and tab-title text to be unreadably small as well; and conversely, if users configure their system such that Firefox's tabs & URL bar are readable, then I would expect this would result in their input-datalist-dropdown text being readable as well.)