[02:18:34] I hear you! @internetam1n had a first design for exactly that, and we even had it implemented and deployed, but then ran into some weird edge cases, and have stepped back from it for now. But we would like to go back there indeed! [09:18:03] Does anyone know why the javascript.includes implementation (Z12711) fails the third test, whereas python in does (Z12863)? [09:26:55] having to wait for the entire ui to load/render every time I click a link is annoying >_< it's even worse than wikidata (that at least mostly renders immediately) [09:35:04] reminds me of being on a dial-up connection... maybe for kids these days, nostalgia will involve looking back and being like "remember when we used to make entire interfaces in javascript" :P [10:00:33] something seems to be wrong with how css is added to the page, on https://www.wikifunctions.org/view/en/Z12696 I get *44* identical sections for .ext-wikilambda-row, and the same for .ext-wikilambda-col and .ext-wikilambda-col-16 (and which for some reason seem to be added dynamically instead of from a css file) : https://tools-static.wmflabs.org/bridgebot/a7319407/file_56883.jpg [10:00:34] https://tools-static.wmflabs.org/bridgebot/e227d41a/file_56884.jpg [10:12:36] the language codes used for the hreflang attribute for those 900+ lines are using mediawiki codes instead of being turned into proper bcp47 codes, e.g. it's using "sr-ec" (which means serbian as used in ecuador) instead of "sr-cyrl" and "hu-formal" (which is an invalid code) [10:13:45] and some of the values include quotes, like hreflang=""simple"" and hreflang=""kmr"" [10:19:24] anyway what I was *actually* trying to look at was the tests section here, because it's scrolling horizontally even though there's plenty of space to the left of it, and if I make it use that space, it doesn't scroll any more : https://tools-static.wmflabs.org/bridgebot/00e8dc28/file_56885.jpg [10:59:37] lemme file a task for this. it might be something that we could address once Codex completes work on T337282 (re @Nikki: something seems to be wrong with how css is added to the page, on https://www.wikifunctions.org/view/en/Z12696 I get *44* identi...) [11:03:56] interesting, so basically we could have the top area of the page for about info and evaluation. and the bottom area for test,s implementations. : https://tools-static.wmflabs.org/bridgebot/00d1d9be/file_56886.jpg [11:06:00] the reason behind the current layout is be ready to accomated upcoming widgets, might this be a "function documentation" widget, or a "where is this function being used?" widget. : https://tools-static.wmflabs.org/bridgebot/d4120ffc/file_56887.jpg [11:09:08] yeah, I think that would make more sense when the window is narrower (my laptop is apparently 1280px wide) (re @internetam1n: interesting, so basically we could have the top area of the page for about info and evaluation. and the bottom area for tests, a...) [13:02:24] Thanks @Habst for fixing this https://www.wikifunctions.org/w/index.php?title=Z12711&diff=76427&oldid=71583 (re @Toby: Does anyone know why the javascript.includes implementation (Z12711) fails the third test, whereas python in (Z12863) passes?) [13:17:51] interesting... why does it need stringifying? [14:51:03] 7167 [14:51:21] thank you (re @join_captcha_bot: Captcha solved, user verified. [14:51:22] Welcome to the group, @Pirate_064) [22:10:51] https://www.wikifunctions.org/wiki/Talk:Z12711 (re @Nikki: interesting... why does it need stringifying?)