Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@Jifuna Searching for the end of the entered text along with the URL is definitely not correct behavior, and it screams of unexpected asynchronity:
> keyboard events
> URL change command to browser chrome {newurl}
> keyboard events
> URL bar cleared
> keyboard events
> newurl appended to URL bar
> submit URL bar
I agree that it isn't an attack vector though -
@exerceo @lbfalvy Fair enough, personally never had any problems with this
-
@Jifuna The nature of single threaded asynchronity issues is that the conditions of their emergence are notoriously difficult to pin down; they don't tend to corrupt atomic types but everything else, all datastructures and wrappers are at risk.
-
@KDSBest I don't see why 2 and 3 would be true.
When you're browsing web with firefox and accidentally opens new window instead of new tab
My boss to me: Holy shit dude I think you have very serious case of OCD.
Me: :/
Some love stories are immortal.
In Firefox, refreshing and redirecting pages steal the URL bar.
When a page refreshes itself or redirects elsewhere while I am entering something into the URL bar, what I entered gets replaced with the URL of the target page that was redirected to, or the URL of the current page if it refreshes itself.
This makes the user vulnerable to spam pages that refresh themselves or keep redirecting to hijack the URL bar.
If this happens the fraction of a second before I press "Enter", Firefox web searches for the end of my search term with the target URL appended to it, for example if I entered "example search term", it would search for "ermhttps://www.example.org".
You'd think this would have been fixed by now, after over a decade, but no.
rant
firefox