Edit report at https://bugs.php.net/bug.php?id=67458&edit=1
ID: 67458 Comment by: malinky at yopmail dot com Reported by: martin dot idealia at gmx dot com Summary: website steals shortcut for quick find in firefox Status: Wont fix Type: Bug Package: Website problem PHP Version: Irrelevant Block user comment: N Private report: N New Comment: Lack of respect for users -- bj...@php.net What makes you think it's ok to waste the world's time - the time they spent typing in a search string, only to discover they were typing it into the php.net search box Previous Comments: ------------------------------------------------------------------------ [2014-07-06 15:12:25] hdfssk at gmail dot com Respectfully, Hannes, âNoâ should not be the last word on this subject; the / keybinding breaks the search-in-page muscle memory for firefox, for an unclear gain⦠how does it help wrt searching the PHP docs? (PS. Iâd much rather have voted on an open bug and moved on than tried to revive a WONTFIX this wayâ¦) ------------------------------------------------------------------------ [2014-07-05 16:40:46] bj...@php.net No. Use a Greasemonkey script to unbind it. I'd recommend loading it globally so you don't have to worry about other websites using it. ------------------------------------------------------------------------ [2014-07-05 12:25:33] sandeepcr2 at gmail dot com Yes, gmail and twitter may have done so. But I think this function, in the context of php.net documentation pages, does more harm than good. Take the example of gmail. There is not much use for searching the text that is in page. Because the contents are short. Most often you are interested in the searching the mails themselves rather than the page contents. But take the case of the php.net. The user has probably done the search in google and arrived at the exact documentation page in php.net. Now this page can have a lot of content. For eg, take the documentation page for cURL extension. There are a lot of flags and options in those pages. So there is a lot of content in the page itself and with out text search it will be hard to find the info user is looking for. So most of the time, the user will have to use the in-page-text search, as opposed to the actual site search. This issue is worsened by the fact that you cannot search for flag constants from the php.net's search function. So I think the slash key should be returned to its default text search function by which it will be most useful. ------------------------------------------------------------------------ [2014-06-17 15:14:34] le...@php.net I understand your pain. I understand that other websites also use this hotkey for search (for instance, twitter and gmail). I'll think about this for a while. ------------------------------------------------------------------------ [2014-06-17 06:44:58] martin dot idealia at gmx dot com Description: ------------ When viewing documentation in firefox, pressing / (forward slash key) should start quick search function of firefox, instead the search input at the top right corner of the page gets focus. Expected result: ---------------- pressing / key should start quick search in current document Actual result: -------------- / press is stolen by search intpu field at the top right corner of the page ------------------------------------------------------------------------ -- Edit this bug report at https://bugs.php.net/bug.php?id=67458&edit=1 -- PHP Webmaster List Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
