Hacker News new | past | comments | ask | show | jobs | submit | pupppet's comments login

I'm sure the syntax for it wouldn't have been pretty but inline styles not being able support pseudo-classes was a real miss.

Once you visualize it as a shirt lifting up over an overweight man’s belly, it’s unseeable forever. I’m sorry.

Exactly, i actually thought they'd changed it back but no, still overweight man belly: https://ogden_images.s3.amazonaws.com/www.utne.com/images/20...

One of the worst logo's in a long time, the font is also garbage.


oh look, it’s a government getting involved with big tech and improving the lives of its citizens. Funny how the just let the market decide folk suddenly go quiet on threads like this.

Crypto more important than electricity?

And crypto doesn’t use electricity, it wastes it in on a completely arbitrary task.


Uh oh crypto bros pushing back


Right up there with hijacking Ctrl-F.


There's a lot of keyboard shortcuts that mean one thing in the browser but something totally different in another application. Now that it is common for many of these other applications to now be a web app, these keyboard short cuts are possible to start colliding.

Take GoogDocs as an example. Do you want the browser's find or the app's find if you hit ctrl-f in a Doc/Sheet/etc? The vast majority of the users want the app's. Reading a news site, most people would probably expect ctrl-f for the browser's search.

Just pointing out that hard rules will always have exceptions. Except for the TFA's point of copy/paste. Stop manipulating my clipboard with bullshit marketing/tracking bullshit!!!!!!!


Then the vast majority of users are wrong. The correct answer is for it be the browser's find.

Maybe apps could bind their find/search to ctrl-s since it is incorrect for browsers to bind this to save-page anyway.


why is all of the sudden ctrl-s wrong by the browser?? you make no sense here. you've never needed to save a web page? i guess i'm showing my age, while i don't use it daily, it has been a valuable feature for many reasons before.

Edit: >Then the vast majority of users are wrong.

I strongly disagree, and people unwilling to be flexible ruins the experience as those people tend to be the minority


You’re absolutely correct though, the parent comment seems to think there are absolute right and wrong answers for UI. I think that’s just not true, a good UI is one that works for your customers.


Of course there are absolute right and wrong answers for UI. Accessibility, minimum text contrast and font size, minimum size for clickable items. Keyboard shortcuts may not be (or may be) one of them, but in fact consistency across applications _is_ considered a hallmark of good UI and every Human Interface Guideline I've ever read, including open source ones such as that from KDE, specify such.


You're being obtuse. Even most of those you list will not reasonably have a fixed, absolute value that is right for all users, all applications, and all situations, and assuming they do is the cause of a lot of awful UI limitations.

(Your user will never need characters to render as single pixels? Try again - sooner or later someone will decide to abuse your spreadsheet as a raytracer and be annoyed they can't make cells single pixel)

And a feeling of consistentency often requires exceptions for specific cases such as the example of "find" where few users want to specifically find what happens to be in the browsers idea of what the document currently contains, but what it logically contains in their model of what it should contain. Consistency means that in an app that dynamically updates a scrollable region, for example, it should still find things in the currently not part of the browser document bits, and so shouldn't use the browsers find in those cases.

Some users might want a shortcut that always does the browsers own find, and there generally ought to be ways to override the app, but consistently acting how the user will want is rarely compatible with absolute rules.


I agree with almost all of the specific examples you give, but I think I agree _because_ those UI decisions work better for customers, and not because they are absolute right and wrong. I think I can illustrate this with some examples:

1. Consider a keyboard without an f-key, eg Arabic. If the user is using an Arabic keyboard, what should bring up the browsers 'find' functionality. Of course ctrl-f won't cut it. Perhaps it should be ctrl-[first letter of 'find' in Arabic]? Or perhaps ctrl-[the letter in the same position as f on qwerty keyboard]? It makes sense to follow convention if one is already established for Arabic, but then what about languages that are new to the web?

2. Consider a phone-tree, which is a sort of UI. For this UI, the 'absolute right answers' of minimum text contrast, font size, keyboard shortcuts, etc, make no sense, but there are surely other ways to make the UI work well for customers.

In both these scenarios, I feel the 'right' choice is to pick the UI that is best for users. I think there isn't a-priori a right answer, and users habits change over time and across cultures, so it's not necessarily an easy choice.


Hey, man. I'm just dispensing justice. I don't make the rules


They're trolling.


The browser's control-f won't find you text draw onto a canvas element so those users really aren't wrong ...


It's also trivial to use Ctrl+F on such pages if you so choose by clicking into the URL bar and then doing the keyboard combo. (Or just make two clicks in the browser menu.)

I can see valid use cases for customizing Ctrl+F.


Discourse apps bind the first hit of Ctrl/cmd-f to the app's search feature, and then the second passes through and hits the browsers. Seems to be the right way to do it


There are semi-legitimate cases where this is warranted. For instance when looking at a Notion database, standard Ctrl-F is almost useless, and document search needs to go through the notion API to return results, sometimes even related to the entries that are displayed on screen.

I say "semi-legitimate" because I actually wish they'd map to a different shortcut, but can see the case for user wanted the remapping.

This of course stems from earlier decisions to have that document handling style in the first place. IMHO it becomes a complex debate when on line between an online application and a webpage.


Shouldn’t CMD+F be reserved to searching the current document/context?

Something like CMD+K should be used for a more global search.


You cant use those keys (Super+) in the browser AFAIK. The operating system expects to use them for keyboard shortcuts.

(Guessing on macOS Cmd+V is actually triggering a clipboard event in JS, the site can’t actually see that you pressed Cmd+V)


Recently learned that if you Ctrl-F again after the highjacking, it brings up the browser search box.

Discovered this thanks to a site (don't remember which) that included a tooltip about this fact in their hijacked search box. I was curious if it would work on Redocly search, which has no such tooltip, and it did. I'm not positive if this works universally, or is just an undocumented feature of Redocly's interface and won't work in places the developers didn't make specific accommodations for it.

Env: Chrome + OSX or Windows.


It's a feature built-in to most browsers, same with right-click (if page hijacks right click, right-click twice in rapid succession).


Thanks for the info!


I just don't get it why browsers allow websites to override their own hotkeys. I'm sure it even required extra code to be written to work correctly.

Linear hijacks Cmd+F for example, very helpfully providing some terrible thing instead of my browser's built-in search that works the same everywhere. (it's the same Linear that thinks you can't not want wysiwyg markdown editing)


Well, for Ctrl+F there is sometimes a reason. Many websites uses technique called virtualization of lists. That boosts performance, but standard Ctrl+F doesn't works anymore properly


I know of 2 websites that do this. 1. Confluence It's super annoying and takes up a lot of screen space 2. Nexus It simply kills it. You can use ctrl-f but it simply will not find text right in front of you..

Really i see no valid case


DOS emulator and Vim emulator, and that's almost all I can imagine. Maybe games that would use the control key as an additional input---but in the browser???


github code editor is a big one


The good sites allow you to hit ctrl f twice to get browser's find feature.


Stripe’s API documentation does this and it gives me the shits, because it seizes up my M2 MacBook Pro for several seconds.

I can’t believe that it’s 2024, and I can’t simply grep some documentation.


The Vimperator/Tridactyl (Firefox VI shortcuts extension) search / is not hijacked on the Stripe API documention.


FWIW, the / search isn't part of Tridactyl but we do inject some code that frees up / from most websites so Firefox can use it.

It's possible to write your own user script to do it (you just need to add a keypress event handler that does preventDefault() and maybe stopPropagation()) with no need for Tridactyl :)


Good to know, thank you. Maybe non-Trydactyl users should check if / is hijacked along with Ctrl-F, Ctrl-G, and F3.

And I'll take the opportunity to say thank you for Tridactyl! Have a great weekend!


But it still doesn't seem to work on GitHub, did you whitelist GitHub for the preventDefault or is GitHub just a bit extra when it comes to hijacking keybinds?


It works sometimes on GitHub, it's just a bit extra as you said.

GitHub is what annoyed me enough to make the feature in the first place. It used to work reliably but they made it worse :(


Ah bummers, but nonetheless thanks for implementing this feature!

EDIT: I just took a look at GitHub's source code, and they mentioned a setting to turn off these shortcuts, and it really exists!! Under https://github.com/settings/accessibility one can turn off, all "Character keys" which means shortcuts without a modifier. I've never used them, so I just disabled it, and now forward slash always opens the Firefox search :0

https://docs.github.com/en/get-started/accessibility/keyboar...


I had no idea, thanks for sharing!


Cmd-L followed by Cmd-F will always get you the real browser search, at least.


And overriding Ctrl+K without even being so good as to give way when you type it a second time. Assholes.


We're talking about you, Slack. (At least I can now remember which app is the one that breaks Cmd-K, but it's still annoying that I have to think that little bit longer to recall that info. every single time I press Cmd-K anywhere)


Hell just hijacking any standard browser controls is infuriating when it catches you out when you're just not paying complete attention.

Edit: Apparently Firefox has the `permissions.default.shortcuts` config option

UNKNOWN: Services.perms.UNKNOWN_ACTION [0]

ALLOW: Services.perms.ALLOW_ACTION [1]

BLOCK: Services.perms.DENY_ACTION [2]

PROMPT: Services.perms.PROMPT_ACTION [3]

And in the site information panel you can disable the Override keyboard shortcuts permission on a per-site basis. Neat, doesn't solve the paste override issue though. Source: https://support.mozilla.org/en-US/questions/1241294#answer-1...


A huge thanks for making me aware of this. permissions.default.shortcuts firmly set to 2.


My personal hate is when webpages rebind scrolling to zoom.

I haven't used a mouse in almost 15 years. It's a constant source of annoyance when I try to scroll something with a map with my trackpad and it goes crazy zooming in and out.


This is the biggest reason why I hate Discourse.


Stripe docs do that and it annoys me to no end. They let you use the native search if you press ctrl+f a second time but since there is a delay it causes chaos.


Ctrl-G and F3 often work to bypass that ime


I honestly didn't know about Ctrl-G. You my have significantly changed my life!


isn't ctrl-g common for "find next" with shift-ctrl-g "find previous"? maybe i live too much in my IDE/text editors?


Almost certainly, but It's one of of these "I can't believe I never knew this, it's so obvious!" things.


In that case, I'd highly recommend browsing through the drop down menus for any of your apps. It is very common* for the keyboard shortcut to be listed, and very frustrating when it is not. This is my primary source for finding these shortcuts for a new app.

* maybe it's a Mac thing???


On macOS cmd+g is a standard shortcut most apps implement.


yeah, i substituted to ctrl from my normal cmd to not confuse people


In my head Ctrl+G is a shortcut for "Ctrl+F with the last result I searched for."


I don't think anyone here can imagine my bewilderment, confusion, and ultimately anger, the day I discovered that in the web interface for Outlook, Ctrl+V is the default shortcut for... send email.

I would very much like to know what went through their heads when they decided on that. On further thought, maybe I don't.



'Find in page' is now so broken on modern websites that the keyboard shortcut is the last of our problems.


Bitwarden.

"Find in page" will only show a result if it is visible on the page (even though the scrollbar indicates the full vault has loaded, and even after scrolling down to the desired result and then back up).

They have a "Search vault" field that works fine, so it's not a major inconvenience, but the first few times I've Ctrl+F'd a newly added site and gotten "Phrase not found" when I know I added credentials? That's a mild anxiety I'd rather not have.

I could be convinced there's a security-related reason for this---in fact, I never really thought about it until now---but then I'd assume anyone able to get access to your vault can use Selenium and fill in the "Search vault" input field.


So much this.


hugeicons replying to them is icing on the cake.


I feel like I've brought kids into a dying world.


as ironic as it might seem given my mental health https://www.youtube.com/watch?v=SJUhlRoBL8M If you are able to make your childern happy ,that is what matters. My parents always provided for us but never fostered a happy household. Death will come for us eventually,happiness is what matters (I have learnt the hard way!!)


Decades of poor leadership.


You forget so much of your childhood, but those bullied moments stick.


The new CEO mantra...nobody got fired for pivoting to AI.


Not yet, at least.


I was on a call this morning where a team had decided to break it to their leadership that genai was not the answer they thought it was going to be. I bet there's going to be a lot of that this year.


This is what is so frustrating about this technology. Everyone seems completely convinced this is going to be bigger than sliced bread but a year later, I haven't seen a truly good killer app. A year ago we had chatgpt, co-pilot, mid journey, and stable diffusion, and today we have basically the some products. I've seen a lot of bad code, a lot of boring prose, and a lot of bad art. Meanwhile there's people breathlessly telling us we'll get agi in 5 years.


The loudest people have the least to say, but I think there’s a lot of smart use cases beyond variation on chat bots.


That certainly wasn't Microsoft, they're still full on the "CoPilot" hype train, launching a confusing spectrum of different services all under the same name and all before they're actually ready


> launching a confusing spectrum of different services all under the same name

.net all over again.


Yes indeed!

Microsoft is so incredibly bad at marketing. And really not great at products too. People don't pick them because they're the best at what they do, but because they're what everyone else uses and they're acceptable. The whole reason for Teams being adopted so heavily is because it comes with office and it's not bad enough to justify paying for something better. But when having used other products that were actually leading in their class, it's sometimes sad being stuck with it.

In this light I do understand their rush to capture the AI market, being first is just how they work.


This assumes they'll ever actually be ready. I'm pretty sure at this point the "reliability problem" is just not solvable.


you're comment is old but what is the reliability problem? If it's the fact that you can't guarantee the same output for a given input then I agree. There are patterns out there where you prompt an llm with a list of functions, their description, and parameters and then ask it to chose one and the params. Then based on the response you call that function and return the results back to the llm to be used as part of the final response to the user's prompt.

If you can't guarantee the output of the llm how can you ever expect this to always work the same? How can you even test it? It may test out ok 99 times but on test #100 it fails. Any hallucination breaks it or, even worse, produces a confident sounding wrong output. Is that the reliability problem you're talking about?


Squeezing it in before the mass-firings of CEOs who tried pivoting to "AI" with no sense of what value this might actually provide anyone


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: