Sorry Jamie, I feel like I'm often editing comments after submitting them to add clarity, or to add something I forgot, and I should be more conscious about the fact that the first version that I submit is the version that shows up in people's emails. --- Emilio, I understand that you would prefer not to swap the `<textarea>` elements, but I want to revisit this and ask whether you see this as _just_ a code maintainability drawback, or if you think there would actually be some sort of functional problem with the solution itself. I certainly recognize that the solution is unorthodox, but I feel confident that it would fit in relatively smoothly with the way the panel logic UI is implemented, and I feel confident in my ability to clearly document and test the behavior as the primary author and maintainer of this code for the foreseeable future. I may be more hesitant to do something like this if it were a core piece of shared infrastructure that would expose an API surface to downstream code consumers, but this is an isolated behavior for a specific UI edge-case, and my opinion remains that I would rather take on the burden of implementing/documenting/maintaining something unusual if it provides a genuinely better user experience for everyone. I'd be happy to tag you as a reviewer and also file a follow-up bug that is clearly linked in the code comments to investigate a more straightforward solution to announcing a `<texarea>` update to assistive technologies. If you see this as a blocker for any sort of technical reason, I'd be very interested to know. Otherwise, I'd like to reassert that I think this would provide the best user experience.
Bug 1894091 Comment 15 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Sorry Jamie, I feel like I'm often editing comments after submitting them to add clarity, or to add something I forgot, and I should be more conscious about the fact that the first version that I submit is the version that shows up in people's emails. --- Emilio, I understand that you would prefer not to swap the `<textarea>` elements, but I want to revisit this and ask whether you see this as _just_ a code maintainability drawback, or if you think there would actually be some sort of functional problem with the solution itself. I certainly recognize that the solution is unorthodox, but I feel confident that it would fit in relatively smoothly with the way the panel UI logic is implemented, and I feel confident in my ability to clearly document and test the behavior as the primary author and maintainer of this code for the foreseeable future. I may be more hesitant to do something like this if it were a core piece of shared infrastructure that would expose an API surface to downstream code consumers, but this is an isolated behavior for a specific UI edge-case, and my opinion remains that I would rather take on the burden of implementing/documenting/maintaining something unusual if it provides a genuinely better user experience for everyone. I'd be happy to tag you as a reviewer and also file a follow-up bug that is clearly linked in the code comments to investigate a more straightforward solution to announcing a `<texarea>` update to assistive technologies. If you see this as a blocker for any sort of technical reason, I'd be very interested to know. Otherwise, I'd like to reassert that I think this would provide the best user experience.
Sorry Jamie, I feel like I'm often editing comments after submitting them to fix typos, to add clarity, or to add something I forgot, and I should be more conscious about the fact that the first version that I submit is the version that shows up in people's emails. --- Emilio, I understand that you would prefer not to swap the `<textarea>` elements, but I want to revisit this and ask whether you see this as _just_ a code maintainability drawback, or if you think there would actually be some sort of functional problem with the solution itself. I certainly recognize that the solution is unorthodox, but I feel confident that it would fit in relatively smoothly with the way the panel UI logic is implemented, and I feel confident in my ability to clearly document and test the behavior as the primary author and maintainer of this code for the foreseeable future. I may be more hesitant to do something like this if it were a core piece of shared infrastructure that would expose an API surface to downstream code consumers, but this is an isolated behavior for a specific UI edge-case, and my opinion remains that I would rather take on the burden of implementing/documenting/maintaining something unusual if it provides a genuinely better user experience for everyone. I'd be happy to tag you as a reviewer and also file a follow-up bug that is clearly linked in the code comments to investigate a more straightforward solution to announcing a `<texarea>` update to assistive technologies. If you see this as a blocker for any sort of technical reason, I'd be very interested to know. Otherwise, I'd like to reassert that I think this would provide the best user experience.
Sorry Jamie, I feel like I'm often editing comments after submitting them to fix typos, to improve clarity, or to add something I forgot, and I should be more conscious about the fact that the first version that I submit is the version that shows up in people's emails. --- Emilio, I understand that you would prefer not to swap the `<textarea>` elements, but I want to revisit this and ask whether you see this as _just_ a code maintainability drawback, or if you think there would actually be some sort of functional problem with the solution itself. I certainly recognize that the solution is unorthodox, but I feel confident that it would fit in relatively smoothly with the way the panel UI logic is implemented, and I feel confident in my ability to clearly document and test the behavior as the primary author and maintainer of this code for the foreseeable future. I may be more hesitant to do something like this if it were a core piece of shared infrastructure that would expose an API surface to downstream code consumers, but this is an isolated behavior for a specific UI edge-case, and my opinion remains that I would rather take on the burden of implementing/documenting/maintaining something unusual if it provides a genuinely better user experience for everyone. I'd be happy to tag you as a reviewer and also file a follow-up bug that is clearly linked in the code comments to investigate a more straightforward solution to announcing a `<texarea>` update to assistive technologies. If you see this as a blocker for any sort of technical reason, I'd be very interested to know. Otherwise, I'd like to reassert that I think this would provide the best user experience.