Timeline for The Stack Overflow Unofficial Patch (SOUP)
Current License: CC BY-SA 3.0
58 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 21, 2021 at 14:58 | comment | added | kvantour | Horizontal scroll bar observed in Chrome 94.0.4606.81 with SOUP 1.56.2. (See meta.stackoverflow.com/q/412439/8344060) | |
| Jan 12, 2021 at 3:59 | comment | added | Ilmari Karonen | @gparyani: I'll see about it. Honestly, in the last year and a half I've mostly lost my interest in maintaining SOUP in its current form, as I no longer believe that SE Inc's business model is long-term viable or aligned with the goal of creating an expert Q&A community. And I've also been kind of busy with my day job. But I'm still willing to remove broken fixes and make other similar minor updates, if I can find some time. And I haven't entirely ruled out the possibility of making SOUP 2.0 some day — although if I do, it'll probably be GNU AGPL licensed. | |
| Jan 12, 2021 at 3:36 | comment | added | gparyani | So I made some PRs recently to fix some bugs that cropped up in SOUP due to SE changes. It would be nice if you handled those. | |
| Jul 31, 2020 at 8:35 | comment | added | Mast | Suspected bug: Why is this suggested edit of a question title displaying peculiarly? | |
| Jun 18, 2020 at 8:33 | history | edited | CommunityBot |
Commonmark migration
|
|
| Jan 3, 2020 at 22:05 | comment | added | gparyani | Filed another GitHub issue: github.com/vyznev/soup/issues/49 | |
| Feb 6, 2018 at 22:12 | comment | added | doppelgreener | @IlmariKaronen Just updated my script to that development branch version; it looks fixed from my end. Good stuff. | |
| Feb 6, 2018 at 22:07 | comment | added | Ilmari Karonen | @doppelgreener: Should be fixed in the development branch. | |
| Feb 6, 2018 at 21:35 | comment | added | Ilmari Karonen |
@doppelgreener: Oh, wait... yeah, I can reproduce that. I was looking in the wrong place for the scroll bar. :/ Anyway, yeah, your diagnosis seems correct, it's the width: 100% that's causing it. Will fix, thanks!
|
|
| Feb 6, 2018 at 21:29 | comment | added | doppelgreener | @IlmariKaronen Sure! Screenshots here: chat.meta.stackexchange.com/transcript/message/6667141#6667141 | |
| Feb 6, 2018 at 21:25 | comment | added | Ilmari Karonen | @doppelgreener: Thanks for the report. Unfortunately, I can't reproduce it (on Chrome 64 / Windows 7), but it's far from the first mysterious scroll bar issue on Chrome. I'll look into it. In the mean time, any chance you could send me a screenshot? | |
| Feb 6, 2018 at 20:12 | comment | added | doppelgreener |
SOUP adds a horizontal scrollbar to pages that include spoiler markup (Chrome 64, Windows 10). See this question](puzzling.stackexchange.com/questions/60176/…) for example. It's the Spoiler ::before element causing the width issue. Removing the width: 100% property seems to fix it, or you can assign position: relative; to the .soup-spoiler class. It seems the combination of width:100% and position:absolute (within the page positioning scope) makes the ::before element be the maximum width of the page itself... or something.
|
|
| Jan 24, 2018 at 17:16 | comment | added | Ilmari Karonen | @gparyani: Either will work, but I guess the GitHub method scales a bit better as more issues get reported over time. At some point, I probably should copy all known issues over to GitHub and just direct people there. On the other hand, not everybody has a GitHub account, so... | |
| Jan 24, 2018 at 17:03 | comment | added | gparyani | General question: do you prefer issues to be filed here as a comment, or on the Issues section in GitHub? | |
| Jan 20, 2018 at 3:51 | comment | added | Ilmari Karonen | @gparyani: Huh... I've no idea what might be causing that. I'll try to test that, but since I'm running Linux at home and don't have convenient access to a Windows box for testing, that may take a while. :/ Thanks for the report, anyway! | |
| Jan 20, 2018 at 3:12 | comment | added | gparyani | In Microsoft Edge, the avatars appear in the wrong spot on this question. See i.sstatic.net/0rNik.png | |
| Sep 26, 2017 at 16:42 | comment | added | Ilmari Karonen | @doppelgreener Thanks for the report. I'll take a closer look in a few hours when I get home. I don't recall there being anything in SOUP that should turn tags yellow, but some style might be getting applied where it shouldn't be. | |
| Sep 26, 2017 at 15:20 | comment | added | doppelgreener |
@IlmariKaronen New bug: something in SOUP is making tag syntax inside tag warnings illegible on RPG.SE. See here: rpg.meta.stackexchange.com/questions/7486/…. Seems to be a rule that turns links in tag warnings yellow (targets body .message.message-warning a) which would also be an issue on our site since our tag dialogs themselves are yellow.
|
|
| Apr 13, 2017 at 12:25 | history | edited | CommunityBot |
replaced http://stackapps.com/ with https://stackapps.com/
|
|
| Mar 20, 2017 at 10:29 | history | edited | CommunityBot |
replaced http://meta.stackexchange.com/ with https://meta.stackexchange.com/
|
|
| Mar 20, 2017 at 9:43 | history | edited | CommunityBot |
replaced http://meta.stackoverflow.com/ with https://meta.stackoverflow.com/
|
|
| Mar 16, 2017 at 16:02 | history | edited | CommunityBot |
replaced http://meta.stats.stackexchange.com/ with https://stats.meta.stackexchange.com/
|
|
| Mar 16, 2017 at 15:48 | history | edited | CommunityBot |
replaced http://meta.french.stackexchange.com/ with https://french.meta.stackexchange.com/
|
|
| Mar 16, 2017 at 15:45 | history | edited | CommunityBot |
replaced http://meta.boardgames.stackexchange.com/ with https://boardgames.meta.stackexchange.com/
|
|
| May 3, 2016 at 10:21 | history | edited | Ilmari Karonen | CC BY-SA 3.0 |
added 1037 characters in body
|
| May 3, 2016 at 9:47 | comment | added | Ilmari Karonen |
@NathanTuggy: That's actually very helpful, and I can see what's going wrong now. (SOUP isn't expecting anyone to call MarkdownConverter.makeHtml() in the background, especially not with intentionally mangled Markdown like Dude, where's my cursor does.) I'll list the incompatibility as a known bug for now, and will take a closer look later to see if I can somehow fix it.
|
|
| May 3, 2016 at 6:21 | comment | added | Nathan Tuggy | @IlmariKaronen: I have a lot, but after a bit of tedious binary searching I narrowed to down to balpha's stackapps.com/questions/3894/dude-wheres-my-cursor (although I still don't know exactly how that interferes — there are no error messages). Sorry to bother you with a report that turned out bogus. | |
| Apr 30, 2016 at 10:08 | comment | added | Ilmari Karonen |
@NathanTuggy: Alas, I still can't reproduce this myself. :( I do get the warning if I delete one or both of the opening dashes from the comment (which is appropriate, since it's not a valid comment without the dashes) and wait a few seconds for the popup to trigger, but it goes away (like it's supposed to) if I put the dashes back. To investigate further, could you check if you get any error messages with the prefix mso300679 hook: logged in your browser's developer console when this happens? Also, do you by any chance have any other user scripts installed that might be interfering here?
|
|
| Apr 30, 2016 at 9:48 | comment | added | Nathan Tuggy | @IlmariKaronen: i.sstatic.net/6rlle.png for example, or I just footled around taking out one or two of the opening characters of a comment, putting them back in, and waiting until the warning showed up. | |
| Apr 30, 2016 at 9:28 | comment | added | Ilmari Karonen |
@NathanTuggy: That's not supposed to happen, as long as the comments are correctly formatted (i.e. <!-- some text here -->). Can you show me a test case where that fails (like a post that gives the warning when edited, or some Markdown I can paste into the editor to trigger it)?
|
|
| Apr 29, 2016 at 23:13 | comment | added | Nathan Tuggy | HTML comments trigger the "Bad HTML that will be silently removed" warning, which is dumb, since they're supposed to be removed. The parser doesn't actually support them directly, so this is understandable, but an irritating glitch all the same. | |
| Apr 16, 2016 at 1:58 | comment | added | Jeff Mercado |
I have 3 tabs pinned, no others, maximized and the browser left on all day. Things tend to start to deteriorate after day 2. (1) Google Inbox (no reload), (2) gaming.SE Home (15min reload), (3) SO Home (5min reload). Tab reloading is done via Tab Mix Plus. I'm not watching about:memory, but memory usage in task manager. Memory without it sits at 700MB. With, it rises to about 1GB after a day, 1.5GB after about two, then things start to fail at around 2.5GB usage.
|
|
| Apr 15, 2016 at 9:15 | comment | added | Ilmari Karonen |
@JeffMercado: I tried to reproduce this issue, but after leaving half a dozen SE tabs pinned overnight and using about:memory to compare things before and after, I'm not seeing any obvious leakage. (In fact, the memory usage dropped by 60 MB or so overnight, presumably because Firefox ran a GC pass at some point.) Looking at your original report above, could you tell me what kind of pages you have pinned (front page / question page / chat? or just give URLs)? Also, you say you have them "refreshing every 15 minutes (5 for SO)"; how are you doing that? With an extension?
|
|
| Apr 14, 2016 at 14:29 | comment | added | Jeff Mercado | I can't say this conclusively yet since I've had to restart a couple of times and couldn't have FF running as long, but I did notice just before resetting this morning (after about 1.5 days), memory usage was a little high. (~1GB instead of ~700MB) I'll have to retry the test again. | |
| Apr 9, 2016 at 11:47 | comment | added | Ilmari Karonen | @JeffMercado: Thanks! I'll try to run some tests myself, although I probably won't have time to do it for a few days at least. | |
| Apr 9, 2016 at 11:21 | comment | added | Jeff Mercado | So after having GM on for 2 days, memory usage is still low. I'm going to restart FF with the script enabled. | |
| Apr 9, 2016 at 11:17 | comment | added | Ilmari Karonen | @angussidney: It's already removed from the devel branch. If I don't have time to make a whole new stable release this weekend, I'll backport the removal to the stable branch. | |
| Apr 9, 2016 at 4:17 | comment | added | angussidney | Comparison: No SOUP (default), vs with SOUP (broken). | |
| Apr 9, 2016 at 4:11 | comment | added | angussidney | Back in v1.16 you patched mse229797. The issue was brought back up recently and fixed by SE. However, SE also changed the height of the hover background effect, which is different to the smaller height of active background enforced by SOUP. So if you remove the code from SOUP for that fix, everything will work properly. | |
| Apr 5, 2016 at 16:05 | comment | added | Jeff Mercado | GM is on. I'll let you know in a day or two how much of a change there is. | |
| Apr 5, 2016 at 8:44 | comment | added | Ilmari Karonen | @JeffMercado: Thanks for the notice, I'll try to look into it. If you have time, is there any chance you could test how the memory usage behaves with GM on but SOUP disabled? | |
| Apr 5, 2016 at 2:43 | comment | added | Jeff Mercado | Not sure if this is necessarily a problem caused by the patch but using it seems to be a huge contributing factor in FF's memory leaks (at least in my case). This has caused problems for me since for a long time and I'm only now trying to keep Grease Monkey disabled. So far, memory usage is pretty low (~600MB) even after a day or two. It used to go up to and beyond 2.5GB in that same amount of time. And this is considering I keep 2 pinned tabs of SE sites, refreshing every 15 minutes (5 for SO). This might be for the GM team or something but just thought you should know. | |
| Dec 17, 2014 at 16:48 | history | rollback | Ilmari Karonen |
Rollback to Revision 13
|
|
| Dec 13, 2014 at 20:46 | history | edited | Ilmari Karonen | CC BY-SA 3.0 |
the chrome issue is stranger than I thought
|
| Dec 11, 2014 at 17:31 | history | edited | Ilmari Karonen | CC BY-SA 3.0 |
added 155 characters in body
|
| Oct 7, 2014 at 14:23 | history | edited | Ilmari Karonen | CC BY-SA 3.0 |
added 147 characters in body
|
| Oct 6, 2014 at 14:03 | history | edited | Ilmari Karonen | CC BY-SA 3.0 |
add http://meta.stackexchange.com/questions/240352/horizontal-scrollbar-for-comment-container
|
| Oct 5, 2014 at 21:51 | history | edited | Ilmari Karonen | CC BY-SA 3.0 |
comment vote count bug is fixed as of SOUP v1.22
|
| Sep 4, 2014 at 21:19 | history | edited | Ilmari Karonen | CC BY-SA 3.0 |
briefly explain your changes (corrected spelling, fixed grammar, improved formatting)
|
| Jul 28, 2014 at 14:04 | history | edited | Ilmari Karonen | CC BY-SA 3.0 |
another Opera issue
|
| Jun 26, 2014 at 23:16 | history | edited | Ilmari Karonen | CC BY-SA 3.0 |
added 62 characters in body
|
| Jun 26, 2014 at 15:19 | history | edited | Ilmari Karonen | CC BY-SA 3.0 |
known bug with markdown editor hooks
|
| Jun 13, 2014 at 12:45 | history | edited | Ilmari Karonen | CC BY-SA 3.0 |
add one known bug
|
| Jan 14, 2014 at 22:16 | history | edited | Ilmari Karonen | CC BY-SA 3.0 |
+note
|
| Jan 14, 2014 at 15:58 | history | edited | Ilmari Karonen | CC BY-SA 3.0 |
never mind, PEBKAC: forgot to allow rackcdn.com in NoScript
|
| Jan 14, 2014 at 15:45 | history | edited | Ilmari Karonen | CC BY-SA 3.0 |
+1 known bug
|
| S Jan 14, 2014 at 8:14 | history | answered | Ilmari Karonen | CC BY-SA 3.0 | |
| S Jan 14, 2014 at 8:14 | history | made wiki | Post Made Community Wiki by Ilmari Karonen |
