User talk:Writ Keeper/Scripts/logoutConfirm.js
Has this broken?
[edit]@Ammarpad, Redrose64, Writ Keeper, Khajidha, Arthur Rubin, Winged Blades of Godric, and Home Lander: the participants of my earlier thread and users who have linked to this script.
I've had this installed for a while. I'm reasonably sure I've seen it work properly in the past, but I've recently noticed it failing. I'll (accidentally) tap on "Log out", and get the "are you sure..." screen. But, when I click "cancel", it logs me out anyway. I've had that happen two or three times on my tablet (running some ancient version of Android/Chrome). I can reproduce it on my desktop (MacOS 10.13.6, Chrome 74.0.3729.169). Is this working for other people? -- RoySmith (talk) 13:54, 23 June 2019 (UTC)
- I'm having the same problem.--Khajidha (talk) 14:12, 23 June 2019 (UTC)
- PS-I'm using Firefox on Windows 7. I don't know all the details of versions. --Khajidha (talk) 14:16, 23 June 2019 (UTC)
- I was notified: but I know nothing of this script. Have you tried posting directly to User talk:Writ Keeper, that being the author of the script, rather to this talk page that is buried deep away with only two watchers (not counting myself)? --Redrose64 🌹 (talk) 15:35, 23 June 2019 (UTC)
- I've read the message and I see the problem, but I'm not sure why it wouldn't be working; nothing should have changed. I'll look into it, but fair warning: I'm dealing with some really heavy shit in real life, so I can't say how quickly I'll be able to figure it out. Might be quick if I need a distraction, might not if I need the time. Writ Keeper ⚇♔ 16:09, 23 June 2019 (UTC)
- OK, thanks for taking a look. But, yeah, real life trumps wiki, so please deal with whatever you've got going on first. -- RoySmith (talk) 16:28, 23 June 2019 (UTC)
- Same problem for me. — Arthur Rubin (talk) 21:48, 23 June 2019 (UTC)
- @RoySmith: I am not sure how often you misclick the link, but another way of effectively preventing this issue is by concealing the link with CSS. I did that awhile, and I never had cause to be bothered by misclick again. If there's any need to logout for what ever reason after hiding, then you just need to search for Special:UserLogout in the search bar. BTW, the css is
#pt-logout { display: none; }. – Ammarpad (talk) 16:40, 23 June 2019 (UTC)- Oh, that's clever! Yeah, I can't think of a time when I've ever wanted to intentionally logout. Thanks for the suggestion! -- RoySmith (talk) 22:13, 23 June 2019 (UTC)
- Exactly how would I put that in my css?--Khajidha (talk) 23:32, 23 June 2019 (UTC)
- @Khajidha: You are to copy the above one-line code and paste it in User:Khajidha/common.css. – Ammarpad (talk)
- Apparently there's more to it than that, as doing that made no difference. --Khajidha (talk) 00:41, 24 June 2019
- My guess is your browser has the old css cached. Try emptying your browser cache. -- RoySmith (talk) 00:43, 24 June 2019 (UTC)
- Hmmm. There's something weird going on with User:Khajidha/common.css. CSS pages are supposed to be protected so only the owner can edit them. For example, if I open an incognito window and try to edit User:RoySmith/common.css while logged out, I can only view the source, not edit it. But, I was just able to make two edits to User:Khajidha/common.css while logged out. I don't understand why I was able to do that, but I'm pretty sure the lack of correct protection is what's keeping the CSS from being loaded. -- RoySmith (talk) 02:37, 24 June 2019 (UTC)
- See WP:VPT#Why can I edit another user's common.css file? -- RoySmith (talk) 02:58, 24 June 2019 (UTC)
- Well, Khajidha, you created the page with invalid extension
.ccsbefore moving it, not sure why you didn't just click my redlink. But it's all Ok since this has now been sorted out. Cheers. – Ammarpad (talk) 06:53, 24 June 2019 (UTC)
- Well, Khajidha, you created the page with invalid extension
- See WP:VPT#Why can I edit another user's common.css file? -- RoySmith (talk) 02:58, 24 June 2019 (UTC)
- Hmmm. There's something weird going on with User:Khajidha/common.css. CSS pages are supposed to be protected so only the owner can edit them. For example, if I open an incognito window and try to edit User:RoySmith/common.css while logged out, I can only view the source, not edit it. But, I was just able to make two edits to User:Khajidha/common.css while logged out. I don't understand why I was able to do that, but I'm pretty sure the lack of correct protection is what's keeping the CSS from being loaded. -- RoySmith (talk) 02:37, 24 June 2019 (UTC)
- My guess is your browser has the old css cached. Try emptying your browser cache. -- RoySmith (talk) 00:43, 24 June 2019 (UTC)
- Apparently there's more to it than that, as doing that made no difference. --Khajidha (talk) 00:41, 24 June 2019
- @Khajidha: You are to copy the above one-line code and paste it in User:Khajidha/common.css. – Ammarpad (talk)
- Exactly how would I put that in my css?--Khajidha (talk) 23:32, 23 June 2019 (UTC)
- Oh, that's clever! Yeah, I can't think of a time when I've ever wanted to intentionally logout. Thanks for the suggestion! -- RoySmith (talk) 22:13, 23 June 2019 (UTC)
- Please see the comment I just left on WP:VPT#Why can I edit another user's common.css file?. The fact that content models don't automatically update if you move a page to a different title and it now includes ".css", ".js", or ".json" at the end (like exactly what happened here) is a security hole that needs to be looked into with a phab ticket. Comments and input there would be greatly appreciated. ~Oshwah~(talk) (contribs) 01:33, 29 June 2019 (UTC)