Try this:
Chrome extension can't do that. Because they're sandboxed you can't touch the pages javascript (for obvious reason really).
You can use message passing but it's clunky and would require it on both ends (which isn't going to happen)
###
Try this:
quote highlighting works because it's part of gaf.
event handlers do not stay attached so quick edit won't work for any of your posts added using live thread. I don't know if there's a way to fix this but you can just open the edit link in another window or something. It sucks, I know.
it can check for edits for the last 100/50 (depending on your page preferences) but it's costly. It's basically just comparing giant blobs of text which causes the browser to freeze for a second or two (I imagine it would be terrible on slower computers). I might make this an opt-in thing or something.
Not to be a total jerk but I was wondering what the current state was.
Ma, NeoGAF is hardly usable for me w/o the extension. :-(
Thanks for the update. Could I disable the page leave warning though?
ok, done. The Chrome version has been updated.
This isn't final I just wanted to get something out. Let me know if you find any bugs (please try and explain what you did and where you were so I can try and replicate it)
There's a couple of new things
- you can now change the update speed (30 seconds, 60 seconds and 2 minutes). Hover over the countdown box for toggles
- If the script is running and you try and leave the page it will warn you (like this). I don't know about you but I've accidentally clicked a link and lost a thread before so hopefully this will help.
It should work on both themes and it uses SVG graphics for all you fancy ass high-dpi users.
jQuery is out so make sure you're using an up-to-date version of Chrome (I think you need >18).
quick edits don't work because Chrome can't communicate with javascript on the page.
non Chrome versions will also be available tomorrow probably.
if you're a nerd you can go poke around the source and laugh. If you want to help I'll put it up on github or something or you can just reply/pm me.
It's late here so I'll see what the damage is tomorrow.
Is it just me, or does it not load any new posts after the end of a page? It wouldn't load any new posts from the next page despite the front page saying there was new posts. I'd have to refresh the page via browser, have the next page appear, then go there and it'd work again until it hit the max 50 posts per page and then no more.
I'll make it an option you can toggle like the update speed. Not right now though. tomorrow.
PSY・S;66822441 said:Quoted images on newly loaded posts can't be enlarged.
I was in the Jesus, Ubisoft thread and loaded the next page.
Clicked on a quoted image on the new page and it wouldn't remain enlarged.
Clicked on other quoted images on the page with the same result.
Clicked on a quoted image on the original page and it worked fine.
Was the page finished loading?
I seem to have some problem with the addon so far. It will often go up to 2-3 min without a refresh and after going away from the computer for 20min, when I came back they were all stopped.
PSY・S;66822441 said:Quoted images on newly loaded posts can't be enlarged
The script keeps a count of how many times it fails and stops when it reaches 5. There's a number of places it can fail (such as a server error) but it also counts if it can't find new posts (because there isn't any or there's a bug and it can't sort the response)
This stops the script running indefinitely when nothing is happening.
The delay between updates is a multiple of the fail count. This gives the script about 20 minutes to find a new post before it stops.
The original idea behind this extension was to make it easier to follow fast moving threads. It's not really designed to be left on all the time (which is also why there's no auto-start option)
You can reset the fail count by clicking on the "update" button while it's running. It will also reset if a new post is added.
Ah I see. Is that new or it always been like that? I don't remember a thread stop refreshing by itself in the past (except when GAF went down or course).
it's always been like that.
Wow that's really weird. It never happened to me before and right now all my tabs are stopping after a little while. Maybe I'm having network issues both at home and at work, I dunno.
it could be a bug. can you explain what you're doing? roughly how long before it stops?
I always have a couple of tabs open that I keep with the Live thread active. I've set up all my threads right after I sent he previous message (if you want a timestamp) and right now, some of them are working fine and some of them are up to 2 or 3 min timers (All of them are setup to normal speed). Eventualy, after 10-15min, some of them will just stop automatically.
localStorage.LiveThread_FAIL_LIMIT = x
that sounds like it's working as intended but I've just checked the old version and you're right it is actually different. The old version had a bug that calculated the delay wrong which is why it went on for so long.
I've just published an update (2.0.1) that will double the current limit which should give you about 40 minutes on normal. You can also set your own limit by setting the localStorage key "LiveThread_FAIL_LIMIT".
To do this you'll need to up the web developer console, run this and then refresh the page
Code:localStorage.LiveThread_FAIL_LIMIT = x
x is the number you want. Default is now 8. It was 4. If you set it to something really high it will probably just run forever. I wouldn't recommend doing that though.
So I'm using it with Firefox/Greasemonkey and I don't see the refresh option/info box or anything like that. I know it's installed, I see it checked under the Greasemonkey icon, but it just doesn't seem to be working.
Any ideas?
Every version that isn't the chrome extension is old and broken. I'll have an update for Firefox and IE10 real soon. I want to make sure there's no bugs before I do that because I can't auto updates those like I can chrome.
Is it just me, or does it not load any new posts after the end of a page? It wouldn't load any new posts from the next page despite the front page saying there was new posts. I'd have to refresh the page via browser, have the next page appear, then go there and it'd work again until it hit the max 50 posts per page and then no more.
Yeah I'm getting the same thing now too.
ok, done. The Chrome version has been updated.
This isn't final I just wanted to get something out. Let me know if you find any bugs (please try and explain what you did and where you were so I can try and replicate it)
There's a couple of new things
- you can now change the update speed (30 seconds, 60 seconds and 2 minutes). Hover over the countdown box for toggles
- If the script is running and you try and leave the page it will warn you (like this). I don't know about you but I've accidentally clicked a link and lost a thread before so hopefully this will help.
It should work on both themes and it uses SVG graphics for all you fancy ass high-dpi users.
jQuery is out so make sure you're using an up-to-date version of Chrome (I think you need >18).
quick edits don't work because Chrome can't communicate with javascript on the page.
if you're a nerd you can go poke around the source and laugh. If you want to help I'll put it up on github or something or you can just reply/pm me.