Backspace navigation

Are they completely retarded? You don't REMOVE access to back navigation via backspace key to due blithering idiots who are incapable of using a keyboard properly without hitting backspace while inputting data. I've been using backspace navigation for over 15 years without an issue. No, extensions don't solve the problem they bog the browser down. Running software just to be able to use a key as always is not a valid solution. The solution is to make it a flag in chrome:flags or make it an option in settings. How can you pea brained chrome developers be so fucking stupid? Hang yourself from a palm tree you god damned morons. I'll be joining the masses in applauding you as you crash and burn, faggots. No intelligent person accepts your form of "logic".

Other urls found in this thread:

productforums.google.com/forum/m/#!topic/chrome/D4VMOXTxPwg;context-place=forum/chrome
bugs.chromium.org/p/chromium/issues/detail?id=608016
twitter.com/SFWRedditImages

i completely agree, they didn't even due it for a good reason

chillax bro... it's only a browser =/

>using Chrome
You deserve it.

Just use your side mouse buttons for backwards/forwards in history

The same people who thought it was brilliant to switch the save image and open image in new tab on the context menu. Fucking idiots

Did they remove that? lmao

no you fucking retard those buttons are even more cancerous than this standardized key removal

CLI arguments don't work either you have to update the shortcut manually every fucking time the browser updates. Off yourself google you stupid fucks.

>No intelligent person accepts your form of "logic".

"Intelligent person" who care about these things don't make up enough people. This is the issue with something becoming a world standard - they have to cater to the masses to keep their userbase.

I don't mind though, I switched to Firefox ages ago, and it performs noticably better than Chrome, at least on linux.

mine works

oh wait. it isn't updated.
nevermind

>not using Chrome
>being this fucking retarded

>nothing can ever change unless I say so!
Fucking gaymergaters really need to leave.

>don't make up enough people
your "argument" (actually failed reading comprehension) already fell flat on its face when they could have made it a flag or setting. there's no fucking reason on planet earth to REMOVE the functionality. even if such behavior is only used 0.0x% of the time those times it is used is mission critical for a SHITLOAD of people when dealing with a browser used by millions.

falseflag retards are the cancer that made moot leave

That's what I've done for years. Its just more efficient.

...

it reduces fine motor control of the mouse. it's not a valid solution.

here's your you

I've really got to say it, huh? They want retards like you to use something else. You and your ilk are a stain on the Google botnet. Your poorfag browsing habits just taint the data they want to sell to marketers and your government doesn't care if you live or die.

You fucking what?

Well, I use side buttons for navigation, but I'm still against this change. Sometimes I'm not holding my mouse while reading an article or page, and I want to go back before putting my hand on my mouse I'll use backspace.

It's also a good fallback for whenever I don't have a mouse with sidebuttons.

Doesn't matter anyway though, you shouldn't be using Chrome in the first place.

0/10

> You don't REMOVE access to back navigation via backspace key to due blithering idiots
Ha, guess what: you do.

Remember, Chrome's main userbase consists of tech illiterates, and Google's main goal is to collect their personal data, not to serve them with quality software and services. If you're not tech illiterate and\or you care about your freedoms and habits and whatnot, use something else.

>you shouldn't be using Chrome in the first place
i can't stand the ui behavior of firefox i've spent hundreds of hours tweaking it over the course of my existence and could never make it feel as snappy as chrome or hell even ie. i also prefer the flash implementation in chrome even tho i rarely use it.

>i can't stand the ui behavior of firefox

The hell does this even mean?

Also, try using a real OS. Firefox works way better there.

still doesn't explain why they didn't make it a flag. they've left all kinds of utterly retarded legacy shit in flags for this very reason. they did this intentionally to piss long time users off and they deserve to be roasted for it.

So, where to move from there? Firefox on going the same path, opera is now chinese...

i've been asking myself this for the better part of a decade. i actually used the original 0.1 build of "phoenix" back in the day and was responsible for a lot of word of mouth advertising of it. it was so lightning fast. there's just this subtle delay when closing tabs and activating other ui elements, can't be more than a few milliseconds compared to other browsers but it drives me insane. i've tweaked the corresponding values in about:config but the delay is still there. i also dislike their flash implementation enough to drop it entirely.

i use chromium in freebsd and lubuntu btw it's not an os thing

> still doesn't explain why they didn't make it a flag
The same reason why they removed vertical tabs toolbar and floating URL bar: because fuck you, that's why. It's also the same reason why most Chrome users got that obscure "YouTube" extension that force-enabled ads on youtube.

WHAT IS ALT+LEFT ARROW? FUCKING IDIOT

if you thought 0.04% was insignificant wait until you see 0.0000000000001% who use alt left.

i wondered why it stopped working

Chrome is not a backwards looking browser. The fact that some legacy browsers used it doesn't make "backspace for back" have any place in Chrome. Setting backspace to back was one of the worst ideas in UI design history and it deserves to die and be buried without comment, not to retain some life as a legacy flag.
If you could pull your head out of your gaymergater ass for a minute you'd see that what you should be asking for is configurable keybinds instead of crying that Chrome's entire design team isn't parked in orbit around your one special snowflake use case.

> Chrome is not a browser
Okay, that explains it.

you didn't include a single point in your whine post you false flagging faggot.

>0.04% of previous page come from backspace!
Note: they get these stats from the inbred morons who don't open links in a new tab when using their search engine aka luddites who barely know how to use tabs to begin with.

Please explain how a conveniently placed keybind could possibly be described as "cancerous" by a rational adult human being.

it reduces fine motor control of the mouse. the thumb is used to grip the mouse and hence nobody who values the god tier precision of a mouse with a flawless sensor would do anything as pants on head retarded as intentionally interfering with the fine motor control of it.

I agree, spacebar to scroll to the end of a page also pisses me off.

>he disagreed with my premise that the world should revolve around me! MUH GAYMERGATE!

You really should use your hashtag.

>I'll be joining the masses in applauding you as you crash and burn, faggots

I think what you meant to say is that you lack the coordination to press the buttons while playing battlefeel pubescent edition and it triggers feelings of inadequacy.

also home page up down end and arrow keys
like, that's what a mouse is for xD

it's usefull for fapping

no i think i enjoy fast and precise pixel perfect precision more than being a dorito crusted finger fatass who can't situp straight who can't learn to use a keyboard properly so they must use their mouse for everything on their pc/gay porn viewer

It doesn't reduce shit. Your thumb still grips the mouse whether or not you are pressing the buttons.

your thumb cannot maintain grip of the mouse while being moved from the side to clicking a side button with it while simultaneously making afast and large sweeping motion to a pixel precise selection. you lose fine motor control, i don't. end of story.

You're forgetting the userbase Chrome caters to.

>using chrom*
>trusting jewggle
>considers himself not a normie
how do you not deserve this?

Mine can, but I just realized that its probably because my thumb is double jointed.

nah you're right. the truth is it's part of a ploy to force users to switch to microsoft/nsa edge because chrome can't be made compatible with their advanced spying tools

>keeps a full un-encrypted copy of everything you have in your browser (sans-cache) in the jewggle servers
>chrome can't be made compatible with nsa advanced spying tools
>jewggle wants you to leave their browser
wut?!?
btw, they already have everything they want about you and your browser on their servers, no need to spy

I FUCKING HATE backspace navigation.

use alt+left/right arrows. you are welcome.

>using two keys instead of one
absolutely retarded

i'm using the extension backsies and shitting on google for the rest of my life

OP, you sound like a retarded faggot. Remember the hypothetical story about the guy who complained when they fixed space bar from causing the CPU to overheat? Yeah, you're that guy.

Moron. (or troll)

>removing functionality is the same as fixing a bug
no user, you are the moron.

only tards use backspace for navigation.

>this damage control

>moving your hands off your keyboard or pressing two keystrokes instead of one is better
retard

I'm sure you can re-add the functionality in an extension. You must be some kind of special.

hey i use that :(

>not having mouse with at least 4 buttons
>not having touchpad with gestures
>being retarded
kek, tard.

extensions add bloat, are a security concern and don't possess the same functionality. only a tech illiterate moron wouldn't immediately realize this.

Adblock/Ublock is also bloat. So are ads. Pick your poison.

>being forced to move hands off keyboard
>reducing fine motor control of the mouse to support your poor keyboarding hanbits
t. googleshill

that's the exact opposite. filtering ads reduces bloat and increases security. you couldn't have selected a worse example.

>dyslexia

Boohoo. 99% of people don't want backspace deleting form data. I'm glad they removed it completely, so that a flag wrongly set could not bring back that retarded "feature".

yes you are

incorrectly interpreting data doesn't mean they don't want it. but i can see google already paid their media outlet buddies tons of money to praise this mentally retarded feature removal meanwhile actual tech forums are filled with complaints and there's not a single logical reason for removing it when they could have made it a setting choice

I'm with you user. I feel the same way about the unified tabs gone from the mobile app.

BEFORE
>tap menu button on the phone
>get all your open tabs and applications in the same bulk

It was perfect. The majority of mobile use is a handful of apps and a ton of websites that sometimes are really nice to keep open

NOW
>tap menu button
>open chrome
>tap the TINY tab icon
>and THEN select the tab

It's absolutely mind fucking boggling as to why they didn't at least keep it as a choice. Some illiterate fucktard probably couldn't tell the difference between a tab and an app so they removed the feature altogether these mongoloid retards. FUCK.

>hey we will now sell cars with 3 wheels because they can still move, you just need to balance your ass in each corner to don't roll over, but if you add an extension wheel that can potentially fuck up your alarm, locks, brakes and steering you'll be right exactly like before.

No wonder google shit on their users, they are apple tier retarded.

>backspace for back navigation
Do you scroll with the arrow keys too?

If only 0.04% of navigations come from backspace, then how on earth can there be many people to request such a change? Evidence indicates not only are there few navigations coming from this but strong evidence indicates those navigations are intentional, not by mistake. As evidenced by the fact that there are now many people complaining, in spite of the fact only 0.04% of navigations come from backspace. So of those 0.04%, it could be argued more than half were intentional.

They are wasting time changing something that cannot logically be concluded is for the better of its users.

meant for

>meanwhile actual tech forums are filled with complaints

You're being BTFO here, and three people sharing your complaint on other forums does not make it an intelligent feature. I missed that clean OS feeling from reinstalling Windows 98 every 2 months, but that doesn't make XP's removal of the bit rot feature a bad decision.

productforums.google.com/forum/m/#!topic/chrome/D4VMOXTxPwg;context-place=forum/chrome

bugs.chromium.org/p/chromium/issues/detail?id=608016

tldr: actual users don't like the change. luddites who don't block google's spying analytics are the 0.04% so even for their target audience it doesn't make any sense as their target audience isn't even making the mistake they claim to be fixing.

The fact is most people who used backspace wanted to, not accidentally. This change is retarded and they need to revert it or make it a setting.

ctrl-shift-q is a much bigger issue

literally the most retarded shortcut I've ever seen

you forgot to include a point in your diarrhea post, retard. i included several in mine and there haven't been a single valid argument against

Browsers are hard.

>my opinion is right because muh fee fees agree!

You forgot your hashtag.

>checked out advanced shortcuts
>z/x for back/forward
>1/2 for tab switching
>configurable
Why didn't I use that shit before.

1. there's no reason to remove backspace navigation as a setting or flag would suffice
2. extensions are not a valid alternative as they add bloat and security risks
3. there's no evidence to indicate the majority wants this change
4. hitting two keys is slower than one

you have no valid response. kys retard

If you don't like it, fork it.

if i don't like it i shit on it until the end of time. deal with it googleshill

You forgot your hashtag

cool false flag, retard

They didn't remove it because of accidental navigation, but because it messes with the keylogger

Gamergate was a bunch of white males throwing a fit at finding out that something in the universe didn't exclusively revolve around them.
Guess what you are, backspace boy?

Funny but true, but if I could filter the backspace character so could they.

didn't read your narrative false flag post, retard

>chrome
Lmaoing @ ur lyfe kiddo

>"Backspace for back kills form entries. We give this a 0/10, and 99.9% of users agree with us on this."
>HOW DARE THEY RATE IT WITHOUT ASKING ME IF "I" LIKE IT! MUH GAYMERGATE!

>Backspace for back kills form entries
assuming that 100% of the backspace entries were accidents, which they aren't, that leaves 0.04% of back navigations coming from them. and if you don't know how to use a keyboard properly, get the fuck off the computer.

>Backspace for back kills form entries.
What.

Maybe not 100% but close enough.

I used Backspace and Shift + Backspace for 20 years every god damned day.

Fuck Chrome, they better put it back as a flag

>close enough
there isn't a shred of data to indicate such in fact it seems there are indeed a sizeable portion of those 0.04% who use backspace for navigation rather than by mistake.

Oh hey, another change for the sake of change that also hurts usability. Seems to be popular in modern browsers.

Legit got MAD about software for the first time in years after googling for an hour to learn it's NOT a setting in flags, just *poof* gone.

Fuck this retarded shit.

Apparently chrome devs are not going to keep it, because they said we can go fuck ourselves.

Comment 23 by da**[email protected], May 17, 2016

> There will not be a flag for this. We prefer that extensions, rather than options, be used to add non-default behavior in most cases.

Why?

Chrome already has a ton of flags.

From a user's perspective, it just doesn't make sense to load an extension that eats up at least 8Mb of RAM, when essentially an "if" in the browser code would take care of that functionality.
Comment 24 by [email protected], May 17, 2016

Team policy is that flags only be used for short-lived testing and be removed afterward. I have spent man-months of time trying to enforce that, and to the degree that exceptions exist that doesn't justify doing otherwise in general. If we wanted this user-controllable in Chrome itself it would be an option, not a flag, and we have fairly few options which we are always trying to condense into fewer.

Using extensions for configurability is general policy, not specific to this issue. Feel free to file bugs if this system is too resource-inefficient or in general has other problems.

(I mention "policy" here without justifying our policies, because I'm not going to spend the time explaining the origins of our policies on this thread, but these policies do have rationale and aren't just capricious.)