Wikipedia talk:Comments in Local Time: Difference between revisions
→Vector 2022: new section |
→Vector 2022: c |
||
Line 55: | Line 55: | ||
This is apparently incompatible with Vector 2022. See {{phab|318600}} -- [[User:RoySmith|RoySmith]] [[User Talk:RoySmith|(talk)]] 19:52, 27 September 2022 (UTC) |
This is apparently incompatible with Vector 2022. See {{phab|318600}} -- [[User:RoySmith|RoySmith]] [[User Talk:RoySmith|(talk)]] 19:52, 27 September 2022 (UTC) |
||
: Thanks for letting me know. I don't see a solution to the problem in that thread yet. I tried Vector 2022 a few weeks ago, but didn't like it, so am sticking with Vector. So if someone comes up with a solution to this issue, then feel free to update the script themselves, or let me know. [[User:Gary|Gary]] ([[User talk:Gary|talk]]) 17:36, 28 September 2022 (UTC) |
Revision as of 17:36, 28 September 2022
This is the talk page for discussing improvements to the Comments in Local Time page. |
|
Archives: 1 |
Timestamp issue
If i get some result which was published at 09.01 am from wikipedia from india the is it showing as UTC based timing or IST based timing? Subha617 (talk) 21:03, 29 June 2020 (UTC)
- Subha617, Wikipedia time is UTC. Ed6767 talk! 21:03, 29 June 2020 (UTC)
Okay i am getting result based on UTC right? Subha617 (talk) 21:05, 29 June 2020 (UTC)
24 hour clock not working?
In User:YueWang12/skin.js and User:YueWang12/minerva.js, I've set twentyFourHours: true
. But I still seeing 12 hour clock (11:26 am, Today (UTC+7)
). Any solutions? Xiao Wang (talk) 04:31, 24 September 2020 (UTC)
- The settings are supposed to go before the `importScript`. Gary (talk · scripts) 17:46, 24 September 2020 (UTC)
Mobile?
Is this gadget OK on mobile WP?
span.style.whiteSpace = 'nowrap';
Why does this include "span.style.whiteSpace = 'nowrap'"? This causes strange layout problems when inside of a narrow box. See the discussion at Special:Permalink/1102169873#Why does this text overflow the page boundary?. -- RoySmith (talk) 18:47, 3 August 2022 (UTC)
- Please note, this gadget is just a call to User:Gary's personal userscript. We don't really do gadgets like that anymore, but we initially did. Gary would need to fix this on his end. — xaosflux Talk 20:31, 3 August 2022 (UTC)
- Gary hasn't edited since April. Maybe we should just interface admin this. —TheDJ (talk • contribs) 08:28, 4 August 2022 (UTC)
- The script uses "white-space: nowrap" to keep all the elements together. An admin can change it if they'd like. A few options are:
- Don't forcefully wrap anything at all, therefore letting the text naturally wrap. Removing the code "span.style.whiteSpace = 'nowrap';" should be enough to do that.
- Wrap smaller groups of text together, rather than the whole thing.
- Gary (talk · scripts) 21:18, 4 August 2022 (UTC)
- I'm having this problem as well. I'd support a solution of some kind. By the way, it only started happening recently. Did this gadget change recently, or did something else change recently and this is just a side effect? –Novem Linguae (talk) 21:21, 8 August 2022 (UTC)
- Aha. I found the root cause: [1] –Novem Linguae (talk) 21:23, 8 August 2022 (UTC)
- The script uses "white-space: nowrap" to keep all the elements together. An admin can change it if they'd like. A few options are:
The problem should be fixed now. I separately wrapped most of the timestamp elements, so that they would still logically stick together, but as a whole, they wouldn't be nowrapped. Gary (talk · scripts) 20:57, 9 August 2022 (UTC)
- I can see that there's now a bunch of smaller nowrap spans, but it's still causing the same problem, although possibly at a somewhat narrower width. We don't use nowrap in other places. I don't see the need to put it here either. Just let things wrap however they normally wrap. -- RoySmith (talk) 23:22, 9 August 2022 (UTC)
- Looking at it closer, I see things like:
<span style="white-space: nowrap;">, Wednesday</span>
- what's the point of disallowing a line wrap after the comma? That makes no sense. -- RoySmith (talk) 23:25, 9 August 2022 (UTC)
- Okay I removed the wrapping completely. Gary (talk · scripts) 00:01, 10 August 2022 (UTC)
- It's working perfectly now, thanks! -- RoySmith (talk) 00:11, 10 August 2022 (UTC)
- Okay I removed the wrapping completely. Gary (talk · scripts) 00:01, 10 August 2022 (UTC)
Wikipedia:Village pump (proposals)?
The CILT script fails to run on Wikipedia:Village pump (proposals). It is fine with the other VP pages and (as far as I can tell) all other places.
Does anybody else see this?
Why does it seem to fail one just this one page? — GhostInTheMachine talk to me 11:56, 7 August 2022 (UTC)
- Removed the {{Skip to bottom}} template from VPR and now all is well. The template adds a button with a
Skip to bottom
link and encloses it in a div that has the mw-parser-output class.
The script intends to find the article body by looking for the div with the mw-parser-output class, and assumes there should only be one. The script could perhaps instead look for mw-parser-output only within mw-body-content? — GhostInTheMachine talk to me 14:54, 7 August 2022 (UTC) - @Izno and Gary: Looks like the fix has to be in the CILT script. I assume that it will not be possible to remove the
mw-parser-output
class from the {{Skip to bottom}} output. From June 2022, themw-parser-output
class is explicitly added during expansion of the indicator tag that the template generates. See T188443 for the recent change — GhostInTheMachine talk to me 15:58, 7 August 2022 (UTC)
- I used your suggestion and targeted the more specific `mw-body-content` class. Gary (talk · scripts) 20:58, 9 August 2022 (UTC)
Vector 2022
This is apparently incompatible with Vector 2022. See T318600 -- RoySmith (talk) 19:52, 27 September 2022 (UTC)
- Thanks for letting me know. I don't see a solution to the problem in that thread yet. I tried Vector 2022 a few weeks ago, but didn't like it, so am sticking with Vector. So if someone comes up with a solution to this issue, then feel free to update the script themselves, or let me know. Gary (talk) 17:36, 28 September 2022 (UTC)