You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm opening a new issue to formally request that the brave://flags/#copy-link-to-text & #enable-text-fragment-anchor flags get re-added as OPT-IN features (disabled by default).
This issue has already been discussed in depth in these past threads, but the latest comments have had low visibility as they've been on closed issues, so I'm creating a new issue:
Linking to text direct on a page is possible in Chrome using #:~:text=sometext e.g. https://example.com/#:~:text=sometext
It has some minor security concerns that are valid, but only exploitable in an environment where the attacker can middleman traffic/DNS
Many users are ok with the security concerns and rely on this feature extensively for working with long documentation & code amonst teams
As it stands Brave's lack of support for this is a significant detractor for me (and others have commented on the issues above indicating similar frustration). I find myself switching back to Chrome regularly because our workflows depend so heavily on being able to hotlink directly to text, and workarounds like the Link To Text Fragment Extension don't seem to work in Brave either.
To be clear I'm only proposing that is added back to brave behind an OPT-IN feature flag to maintain feature parity with Chrome, I'm NOT proposing that it be re-enabled for everyone by default.
The text was updated successfully, but these errors were encountered:
Platforms
all
Description
I'm opening a new issue to formally request that the
brave://flags/#copy-link-to-text
&#enable-text-fragment-anchor
flags get re-added as OPT-IN features (disabled by default).This issue has already been discussed in depth in these past threads, but the latest comments have had low visibility as they've been on closed issues, so I'm creating a new issue:
brave://flags/#copy-link-to-text
should be disabled by default #17994To summarize:
#:~:text=sometext
e.g.https://example.com/#:~:text=sometext
As it stands Brave's lack of support for this is a significant detractor for me (and others have commented on the issues above indicating similar frustration). I find myself switching back to Chrome regularly because our workflows depend so heavily on being able to hotlink directly to text, and workarounds like the Link To Text Fragment Extension don't seem to work in Brave either.
To be clear I'm only proposing that is added back to brave behind an OPT-IN feature flag to maintain feature parity with Chrome, I'm NOT proposing that it be re-enabled for everyone by default.
The text was updated successfully, but these errors were encountered: