#1645 posted by
- on 2013/02/28 00:01:37
doesn't seem to do so on Firefox
Just Checking About The Refresh Thing
#1648 posted by
necros on 2013/03/02 21:22:51
on firefox 19
#1649 posted by
necros on 2013/03/02 23:50:04
could you make the "All XXXX, Last 25, New XX" bit not get split up by text wrapping?
Yeah, Opera Rocks
#1651 posted by
Spirit on 2013/03/04 17:50:32
All the recent double posts make me wonder if some browser stopped warning on resending post data on a refresh.
Opera does not seem to resend at all which of course is desirable.
Let's see:
Hurr
#1652 posted by chromium on 2013/03/04 17:51:29
durr
#1653 posted by chromium on 2013/03/04 17:51:52
I am a good browser, I prompt.
Herp
#1654 posted by Firefox 19 on 2013/03/04 17:52:20
derp
#1655 posted by Firefox 19 on 2013/03/04 17:52:59
I behave like Opera, not resending, not prompting.
And This Concludes Our Scientific Experiment
#1656 posted by
Spirit on 2013/03/04 17:54:18
The conclusion is that people are using Internet Explorer 4.0
Weird. Make gamma rays or moon phases?
Nope
#1657 posted by
ijed on 2013/03/04 18:21:21
As I stated before, Chrome.
#1660 posted by
rj on 2013/03/04 19:04:56
that was chrome, but it prompted first. don't know why i clicked yes
Feature Request
#1661 posted by
Spirit on 2013/03/05 20:10:35
metl, could you make an anchor in view_thread.php right after the top-most pagination before the first rendered post? And then point to that in "New X" links.
Would save at least 42 milliseconds of scrolling whenever one visits posts with long main posts. ;)
#1664 posted by
metlslime on 2013/03/14 08:00:53
So Firefox (and every other browser once upon a time) lets you refresh without posting, Chrome offers to resubmit the form. I'm not sure why it offers that, since i use a redirect to help clear out the form data (so that people can refresh the page without worries.) Chrome is just too clever; I guess i'll need to find another way.
#1665 posted by
Spirit on 2013/03/14 08:35:08
It's amazing and sad how many people seem to click yes without thinking though. I hope they don't do that for java applets.
One Common Solution
Is to store a magic value in the session and in a hidden form field. On submit, the session value is removed. If the session value is missing, nothing gets posted.
#1668 posted by
RickyT33 on 2013/03/14 08:53:42
Or manually kill the $POST vars after submission maybe.... ?