[02:37:26] Hello Everyone, Please look at https://phabricator.wikimedia.org/T176287 I think it need to remerged. If Any Deployment Window have in this mroning. Please merge it. Thanks [02:42:06] I think nobady is online. can anyone hear me. [02:50:05] Hello [09:11:02] Huh? : [09:11:03] Error: https://commons.wikimedia.org/wiki/Special:Contributions/BehnamFarid at line 24: SyntaxError: missing } after property list [09:11:54] it seems to be somewhere in php code [09:16:36] ankry, huh? And where to see that? [09:17:33] https://commons.wikimedia.org/wiki/Special:Contributions/BehnamFarid [09:18:07] andre__: in the dynamic frame showing for a while after page is loaded [09:18:29] at top-right corner [09:19:54] ankry: not existing here. [09:20:03] check your gadgets, I guess [09:20:15] maybe depends on user preferences [09:21:20] ankry: that error is a JS error, not php [09:21:37] probably from a gadget, as andre__ suggested [16:20:25] Special:Search is looking messed up for me on en.wikipedia.org [16:20:56] like how? [16:20:59] as the search in namespace selector is like only on the right hand side of a page [16:21:12] * bawolff checks other wikis [16:21:15] ah yeah [16:21:40] oh, hmm. Its fine on frwiki [16:22:21] #mw-searchoptions has "margin: -1px 0 0;" [16:23:20] So someone missed an extra 0 maybe [16:32:21] Looks like 052abe72 [16:33:02] Volker_E: ping [16:38:29] https://phabricator.wikimedia.org/T176499 [19:07:09] bawolff: pong [19:10:08] bawolff: `fieldset` is a special beast in browsers, it's one of the least tamable HTML elements CSS-wise [19:11:59] bawolff: I still don't fully understand what's wrong and especially in which browser? Screenshot/browser version would help [19:12:11] *wrong on your side [19:13:03] Volker_E, baw[tab] is not online. ;-) (tab-complete is helpful in multiple ways!) [20:15:06] Volker_E: I added a screenshot, I can reproduce it [20:15:51] legoktm: very weird, I've tried it in Monobook as well [20:16:04] I can repro in Vector too [20:17:05] Volker_E: I'm using Firefox 55 on Fedora if that's useful [20:17:29] ohh [20:17:57] figured it out :) [20:18:18] legoktm: would you add your browser info to the screenshot [20:18:23] legoktm: ok, what's going on? [20:18:29] Volker_E: I have zoom set to 120%. Resetting it to 100% makes the layout look normal. In Chromium zoom levels 100%-125% look fine though [20:18:39] ha [20:18:50] yes [20:18:51] ! [20:19:43] `fieldset`s again [20:19:47] they are so fucked up [20:19:47] (and I'm pretty sure bawolff also increases his zoom level) [20:19:56] yeah, it makes total sense now [20:22:18] legoktm: also bad surprise (I've never experienced this before), on Chrome zooming in changes looks of default inputs completely [20:23:05] the checkboxes? they look relatively same to me [20:24:26] https://usercontent.irccloud-cdn.com/file/sTuEau6j/image.png [20:24:28] 100% [20:25:15] 110% https://usercontent.irccloud-cdn.com/file/5dniqBJY/image.png [20:25:27] o.O [20:25:35] crazy [20:25:53] my checkboxes always look like your 110% [20:26:08] must be a Chrome/Mac bug [20:27:35] lego [20:28:22] I have Chromium from Fedora [20:28:24] legoktm: could you try my salvation tactic: Adding a `clear: both;` to `#mw-searchoptions` on both browsers when zoomed in [20:28:35] sure [20:31:33] I'm actually preparing a patch anyways [20:31:47] Volker_E: works for me. [20:31:53] great [20:32:18] interestingly I only see the bad layout at zoom levels 101%-199%. At 200% the bug goes away (without clear: both) [20:42:21] legoktm: fieldsets have so many rendering quirks attached, one could write a book about it [20:42:45] hah :< [20:45:20] legoktm: thanks for instant patch review [20:45:26] another mystery solved [20:45:28] np :) [23:24:50] Trizek: still in time for https://phabricator.wikimedia.org/T124742#3628806 ?