26-08-2025 09:06 PM - edited 30-05-2026 10:28 PM
To: The Mozilla Community and Development Team
Re: Feature Request: Enhanced Video Quality Switching & Feedback (building upon the existing discussion thread)
This document serves as a comprehensive submission of feedback that expands upon the original feature request and highlights broader user experience and feedback-collection challenges that may benefit from further consideration.
This issue, while seemingly narrow in scope, illustrates a broader challenge in balancing web standards, compatibility, and user expectations.
For an extended period, Firefox for Android users have been unable to select and copy text from YouTube comments when using the default mobile website.
From a user's perspective, this represents a limitation of a common and expected action. On several other Android browsers, including Chrome, Samsung Internet, and Opera, text selection within YouTube comments is currently available and functions as users would expect.
As a result, users who frequently need to copy information from comments may feel compelled to use alternative browsers or adopt workarounds.
Developer responses documented in Bugzilla (Bug 1642073) and WebCompat (Issue #65492) indicate that Firefox's behavior is consistent with web standards because the relevant elements are marked with user-select: none.
From this perspective, the issue originates from YouTube's implementation rather than Firefox itself.
While the standards-based interpretation is technically understandable, users typically evaluate browsers based on functionality and outcomes rather than implementation details.
When a feature works in competing browsers but not in Firefox, users may perceive the limitation as a browser issue regardless of where the underlying cause originates.
This creates an opportunity to consider whether practical compatibility solutions could complement standards compliance in situations where widely used websites significantly impact the browsing experience.
This situation highlights the broader challenge of navigating the relationship between standards adherence and real-world usability.
One possible explanation is that YouTube intentionally restricts text selection to maintain consistency across its platforms, including its native mobile application. If that is the case, it may be unlikely that YouTube will prioritize changes specifically intended to improve compatibility for a particular browser.
In such situations, Firefox users ultimately judge the experience based on whether the functionality is available.
When compatibility issues persist for long periods without resolution, the burden is effectively placed on Firefox users rather than on the website responsible for the implementation.
The existence of browser extensions and user-side modifications that successfully restore text selection suggests that technical solutions may be available.
Exploring targeted compatibility improvements for high-traffic websites could help Firefox better align with user expectations while continuing to support web standards and interoperability.
The YouTube issue also highlights a broader challenge regarding how feedback reaches Mozilla.
Firefox currently relies heavily on platforms such as Bugzilla, GitHub, Connect discussions, and WebCompat reporting channels. While these systems are highly valuable for technical contributors and advanced users, they may be less accessible to the broader user base.
Most users encountering a problem are unlikely to:
Instead, many users may simply conclude that a feature is not working properly and move to another browser that better meets their immediate needs.
As a result, valuable user feedback may never reach Mozilla's teams.
Many modern applications include integrated feedback mechanisms that allow users to quickly:
These systems often guide users through a simplified process while automatically routing feedback to the appropriate teams.
An in-app feedback experience could:
Consider evaluating whether a targeted compatibility solution for YouTube's mobile site could restore text-selection functionality while maintaining Firefox's broader standards-based principles.
Consider developing a streamlined, in-app feedback system that enables users to submit bug reports, feature requests, and usability concerns without leaving the browser.
Such a system could complement existing platforms like Bugzilla and Mozilla Connect rather than replace them.
Standards compliance remains an important strength of Firefox. However, there may be opportunities to complement that approach with pragmatic compatibility solutions when widely used websites create significant usability limitations for Firefox users.
The YouTube text-selection issue serves as a useful example of broader challenges involving compatibility, user expectations, and feedback accessibility.
By exploring targeted compatibility improvements and making feedback submission more approachable for everyday users, Firefox can strengthen its commitment to user experience while continuing to champion an open and standards-based web.
These efforts would not only address specific pain points but also help Mozilla better understand and respond to the needs of its broader user community.
27-08-2025 01:31 AM - edited 27-08-2025 01:32 AM
not 100% sure, but it's likely a youtube decission to have the comment text not selectable , like by just setting the user-select option (ref. https://developer.mozilla.org/en-US/docs/Web/CSS/user-select )
If you have uBlock Origin installed (which you should), you can add a "My Filters" rule to overwrite the user-select which should allow you to select any text you want.
##*:style(-webkit-touch-callout: default !important; -webkit-user-select: text !important; -moz-user-select: text !important; -ms-user-select: text !important; user-select: text !important;)
Obviously you can do this with violentmonkey or any other userscript/style manager too, just be aware that youtube is kind of a special site that doenst completely reload each page when you swich videos but uses ajax to rebuild its content, so that means your modification triggers need to account for that.
28-08-2025 12:21 AM - edited 31-08-2025 10:06 PM
i edited the whole post and clarify everything.
Please upvote.
22-10-2025 02:32 AM
It’s a detailed report highlighting major user experience issues and deeper design or vision mismatches that need correction.
27-10-2025 10:25 PM
If i you agree then like and support this please.
07-11-2025 02:53 PM
I am using Firefox Browser 144.0.2 (64-bit). Since the last update to the browser it has been randomly freezing up my PC to the point that I have to turn it off and back on again. I am running Windows 11 Pro build 26100.6899.
This freezing of my PC only started after the last browser update. Is there a way I can roolback updates like I can in Windows 11?
16-11-2025 09:36 AM
I am android firefox browser app user.
But i suggest to find solution on reddit and if not available post on some good subreddit then you may get help by experts.
Also you can try commenting on experts comment by adding all details and your try in one so you can get answer in one go.
28-03-2026 01:31 PM
I recognise this will sound like hyperbole but I don't care. The UI change might be the straw that broke my camel's back. I was BARELY holding it together with everything going on. You people did this. I want you to straight up know that if I kill myself over the next few days it was this that tipped the scales. Stop ruining EVERYTHING, jfc.