Perl 6 - the future is here, just unevenly distributed

IRC log for #metacpan, 2013-11-18

| Channels | #metacpan index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:59 dsteinbrunner joined #metacpan
02:27 klapperl_ joined #metacpan
02:56 bowtie_ joined #metacpan
03:04 metacpan joined #metacpan
03:04 metacpan [metacpan-web01] oalders pushed 2 new commits to master: http://git.io/3SmrFA
03:04 metacpan metacpan-web/master 7c8b1d6 Gabor Szabo: add rel=author links to Google+ to pod and release pages in order to provide Author information to Google
03:04 metacpan metacpan-web/master 552ecda Olaf Alders: Merge pull request #991 from szabgab/googleplus...
03:04 metacpan left #metacpan
03:04 dipsy [ Comparing 64341f671408...552ecdadcafc · CPAN-API/metacpan-web · GitHub ]
03:49 thaljef joined #metacpan
04:12 preflex_ joined #metacpan
05:56 Farow joined #metacpan
06:27 [Sno] joined #metacpan
08:14 dpetrov_ joined #metacpan
08:24 kentnl joined #metacpan
12:28 dsteinbrunner joined #metacpan
13:40 kentnl_ joined #metacpan
15:28 castaway hmm.. wtf is my "google+ id"?
15:31 daxim example https://profiles.google.com/108247278178090416113
15:31 dipsy [ Lars D?????? - Google+ ]
15:31 daxim that long number is your id
15:32 castaway .. and how did you find it?
15:32 castaway ah, view profile
15:32 castaway ta
15:35 castaway daxim++
15:35 castaway connect all the things!
16:56 ether I was wondering how the google+ PAUSE ID thing was going to work
16:56 ether but I see that we would embed our google+ id in the html, and google search results would see that and treat it specially
17:08 tianon joined #metacpan
17:29 thaljef joined #metacpan
17:34 tianon joined #metacpan
17:35 [Sno] joined #metacpan
17:52 rwstauner it was working before that pull req, but this might be a new google thing
18:03 daxim this whole affair is because googlers are morons
18:12 tianon joined #metacpan
18:36 ether that's a a pretty broad brush you're wielding there
19:12 Mike-PerlRecruiter_ joined #metacpan
19:34 rwstauner joined #metacpan
19:58 rwstaune` joined #metacpan
20:49 cooper joined #metacpan
21:41 b_jonas argh! this javascript history dropdown menu for the metacpan search bar is annoying, is there a way to disable it?
21:42 ether how is it annoying? is it trying to match the wrong things?
21:42 b_jonas I mean, the default history dropdown for text input boxes in firefox is annoying already, because if I move the mouse over an entry then press enter, that entry is loaded; but this metacpan history dropdown is worse: even if I don't move the mouse but it happens to be over an element and I press enter it chooses that
21:43 b_jonas so typically I type something to the searhc bar and press enter, and the mouse just happens to be in the dropdown, so something completely different is selected
21:43 b_jonas why can't these things choose an entry only if I actually click the mouse, or move the selection bar into the dropdown with the keyboard eg. down arrow key?
21:44 trs b_jonas: I don't see that behaviour in Chrome.
21:44 trs b_jonas: that is, if the mouse is below the search box and I start typing int he search box, none of hte autocomplete options are selected.
21:44 trs I have to actually move the mouse again
21:44 b_jonas I yearn the old days when just moving the mouse never had effects in the gui because the cpu wasn't fast enough to bother with that kind of thing
21:45 b_jonas trs: do you wait a few seconds till the results load?
21:45 trs yes.
21:45 b_jonas dunno then, it could be a browser difference
21:45 b_jonas this happens in iceweasel 3.5.16 linux
21:45 trs the results load, and cover the mouse, but nothing is selected unless I move the mouse after the results load (and it's over the results, of course)
21:45 trs so, an ancient firefox.
21:45 b_jonas yes
21:46 trs good to know.
21:46 grantm seems to do it in my FF25 too
21:46 trs yep, same.
21:46 b_jonas and I can't just disable javascript completely for metacpan, because it's used for sorting some things
21:47 trs well, FF23 for me
21:47 b_jonas of course I can disable it and reenable it when I want to sort stuff, but that's clumsy
21:47 b_jonas hmm, what if I set up a keyword for the url bar? that could work
21:47 trs b_jonas: I would argue that this is a bug in the autocomplete when running under FF and it should be fixed.
21:47 trs b_jonas: I <3 url bar keywords
21:47 grantm I tend to agree
21:48 b_jonas I wish even moving the mouse didn't produce any effect for normal input boxes... but that's not a metacpan thing
21:48 grantm I'd never seen this behaviour because I also <3 url bar keywords
21:48 trs Chrome appears to DTRT, which I expect is partly out of security so people can't be tricked into clicking things (clickjackign)
21:50 trs b_jonas: well, moving the mouse over the autocompleter is interacting with it.  I suppose the autocompleter could have select on hover disabled.
21:50 trs I'm not sure if that would break other people's usage :)
21:50 b_jonas that's an old problem started in windows 95 I think
21:51 b_jonas I think it was windows 95 that first had submenus pop up for just hovering
21:51 b_jonas recent guis just made it worse
21:51 trs there are cases where reduces clicks via hover is really nice
21:51 b_jonas possibly
21:51 trs but those cases are less and less as more and more people don't have hover (touchscreens)
21:52 trs s/reduces/reducing/
21:52 b_jonas but if I really want submenus to pop up, I can just drag starting from the main menu.
21:54 trs you're talking to someone who swears by focus follows mouse ;)
21:54 trs and is only recently learning to deal without it on a new work machine (a mac)
22:00 trs anyway, the easiest way to fix this is going to be disassociating highlighting with the mouse and submitting with the keyboard.  it should be sufficient to allow highlight with keyboard, submit with keyboard or click with mouse.
22:03 haarg highlighting on mouse move is a lot nicer visually, but it shouldn't highlight until you start moving the mouse
22:04 trs haarg: sure, but I'm betting that's going to be a harder, more tedious and browser-specific fix, for not necessarily much gain.
22:05 haarg i'm not sure why it would be
22:09 trs haarg: because the autocompleter is just hooking the mouseover event.  and it's the generation of that event which is emitted in different cases on different browsers.
22:10 trs anyway, metacpan could visually highlight on mouseover without actually selecting the suggestion so that enter doesn't submit it, and then everyone would be happy (except for those folks who expect to highlight+select with mouse and press enter)
22:19 haarg trs: you are right about it being browser specific
22:19 haarg but wrong about it being harder to fix
22:19 haarg because it's already fixed in the latest jquery ui
22:20 trs haarg: metacpan doesn't use the jquery ui autocompleter.
22:20 trs :)
22:20 haarg the autocompleter it uses was integrated into jquery ui
22:21 trs yes, and the integrated version is crap compared to the dead simple original one.
22:21 trs I've been down this road before.
22:22 trs jQuery(".ac_result ul").unbind("mouseover") at the correct time fixes the issue b_jonas sees in FF.
22:23 trs haarg: that said, no one is going to argue with you if you move to the jquery ui one and the bug gets fixed. :)
22:24 oalders moving to the jquery ui autocomplete sounds fine
22:41 BBYRD joined #metacpan
22:41 chansen joined #metacpan
22:44 GumbyNET5 joined #metacpan
23:10 Farow joined #metacpan
23:13 b_jonas thank you
23:36 dsteinbrunner joined #metacpan

| Channels | #metacpan index | Today | | Search | Google Search | Plain-Text | summary