https://bugzilla.wikimedia.org/show_bug.cgi?id=40059
--- Comment #2 from [email protected] <[email protected]> 2012-09-07 15:47:53 UTC --- Gerrit is really horrible for browsing... at least if you don't know how-to like me. Loading takes ages and there is no proper syntax-highlighting :-(((( ...and Bugzilla is messing with the links. (In reply to comment #1) If you put a string in, you can't expect useful output. If a callback is supplied and a non-parseable-string was supplied, there are 3 possibilities: # Don't callback. # Callback with the string. # Raise an error. I would prefer #2 or #3. Before, it did #2 and it added the string. Now it does neither callback when supplying a string nor it adds a badge. The callback execution is was not "unreliable" but predictable. Just the arguments passed through the callback depended on the input. But where is the problem with that? After reading the comments in the commit message (is there an easier way to watch them without having to open *each patchset*?), I've the feeling one must read a handbook before one will be able to use gerrrrrrit. For $('<elem>') or $('<elem/>'), why not reading the jQuery-doc? http://api.jquery.com/jQuery/#creating-new-elements -- Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
