Comment #90 on issue 2636 by mkennedy...@comcast.net: Cache form data so
edits are not lost if you naivgate and then come back
http://code.google.com/p/chromium/issues/detail?id=2636
Hey---I just installed Chrome...and frankly am impressded with the speed and
simplicity of it...Hats off to Goo
Comment #89 on issue 2636 by anom2685: Cache form data so edits are not
lost if you naivgate and then come back
http://code.google.com/p/chromium/issues/detail?id=2636
I just lost about an hours work due to this bug. Not only did it not save
my submitted
form when I clicked back, but it also
Comment #78 on issue 2636 by christop...@sbcglobal.net: Cache form data so
edits are not lost if you naivgate and then come back
http://code.google.com/p/chromium/issues/detail?id=2636
I tried out jmyoder's brokenforms.php link using the beta version of Chrome
(2.0.169.1), and there's still a
Comment #77 on issue 2636 by massimo.milan: Cache form data so edits are
not lost if you naivgate and then come back
http://code.google.com/p/chromium/issues/detail?id=2636
Just downloaded the unofficial chromium build for mac osx, and the bug
seems to be
fixed.
--
You received this message
Comment #76 on issue 2636 by jmyoder: Cache form data so edits are not lost
if you naivgate and then come back
http://code.google.com/p/chromium/issues/detail?id=2636
Actually I think my bug report was erroneously merged with this one. My
bug manifests
in this case when you press back a sec
Comment #75 on issue 2636 by jmyoder: Cache form data so edits are not lost
if you naivgate and then come back
http://code.google.com/p/chromium/issues/detail?id=2636
Tested in 2.0.172.2 (which lists this bug as fixed) and this is still
broken. My bug
report was merged with this one but I h
Comment #71 on issue 2636 by www.davidhartley.com: Cache form data so edits
are not lost if you naivgate and then come back
http://code.google.com/p/chromium/issues/detail?id=2636
how is this fixed ?
I am on the beta branch & still have this problem !
(I hate it !)
--
You received this messag
Comment #74 on issue 2636 by fin...@chromium.org: Cache form data so edits
are not lost if you naivgate and then come back
http://code.google.com/p/chromium/issues/detail?id=2636
I'm not sure we have cut a Dev build that includes this fix. In fact, I
think we
haven't - but you are on the rig
Comment #73 on issue 2636 by www.davidhartley.com: Cache form data so edits
are not lost if you naivgate and then come back
http://code.google.com/p/chromium/issues/detail?id=2636
thanks Chris !
I've just updated to dev branch & v.2.0.171.0
I'm looking forward to the possibility of not seeing
Comment #72 on issue 2636 by chris604: Cache form data so edits are not
lost if you naivgate and then come back
http://code.google.com/p/chromium/issues/detail?id=2636
David Hartley, I believe Fixed means it is fixed on the current test builds
(hourly
builds), or possibly the Dev branch buil
Comment #70 on issue 2636 by phajdan...@chromium.org: Cache form data so
edits are not lost if you naivgate and then come back
http://code.google.com/p/chromium/issues/detail?id=2636
Issue 3840 has been merged into this issue.
--
You received this message because you are listed in the owner
o
Comment #66 on issue 2636 by bugdro...@chromium.org: Cache form data so
edits are not lost if you naivgate and then come back
http://code.google.com/p/chromium/issues/detail?id=2636
The following revision refers to this bug:
http://src.chromium.org/viewvc/chrome?view=rev&revision=12374
-
Updates:
Labels: -Mstone-2.1 Mstone-2.0
Comment #65 on issue 2636 by da...@chromium.org: Cache form data so edits
are not lost if you naivgate and then come back
http://code.google.com/p/chromium/issues/detail?id=2636
I've got a working prototype that I'm polishing for review. The Web
Updates:
Labels: -Area-WebKit Area-BrowserBackend
Comment #64 on issue 2636 by da...@chromium.org: Cache form data so edits
are not lost if you naivgate and then come back
http://code.google.com/p/chromium/issues/detail?id=2636
(No comment was entered for this change.)
--
You received
Updates:
Status: Assigned
Owner: da...@chromium.org
Comment #63 on issue 2636 by da...@chromium.org: Cache form data so edits
are not lost if you naivgate and then come back
http://code.google.com/p/chromium/issues/detail?id=2636
(No comment was entered for this change.)
--
Yo
Updates:
Labels: -Mstone-2.0 Mstone-2.1
Comment #62 on issue 2636 by s...@chromium.org: Cache form data so edits are
not lost if you naivgate and then come back
http://code.google.com/p/chromium/issues/detail?id=2636
It's a bit late to consider this for 2.0, so I'm pushing to 2.1. If a
Updates:
Cc: -b...@chromium.org -s...@chromium.org
Labels: -Pri-2 -Area-BrowserUI Pri-1 Area-WebKit
Comment #61 on issue 2636 by j...@chromium.org: Cache form data so edits are
not lost if you naivgate and then come back
http://code.google.com/p/chromium/issues/detail?id=2636
M
Updates:
Status: Available
Owner: ---
Cc: rvar...@chromium.org da...@chromium.org dglaz...@chromium.org
b...@chromium.org s...@chromium.org j...@chromium.org
Comment #60 on issue 2636 by s...@chromium.org: Cache form data so edits are
not lost if you naivgate and then
Updates:
Owner: s...@chromium.org
Labels: -Area-BrowserBackend Area-BrowserUI
Comment #59 on issue 2636 by j...@chromium.org: Cache form data so edits are
not lost if you naivgate and then come back
http://code.google.com/p/chromium/issues/detail?id=2636
Ben suggested Scott.
-
Updates:
Status: Assigned
Owner: j...@chromium.org
Comment #58 on issue 2636 by j...@chromium.org: Cache form data so edits are
not lost if you naivgate and then come back
http://code.google.com/p/chromium/issues/detail?id=2636
Looking for a new owner.
--
You received this mes
Updates:
Status: Untriaged
Owner: ---
Labels: -Pri-1 Pri-2
Comment #57 on issue 2636 by m...@chromium.org: Cache form data so edits are
not lost if you naivgate and then come back
http://code.google.com/p/chromium/issues/detail?id=2636
asargent is not working on this. W
Comment #51 on issue 2636 by johnywhy: Cache form data so edits are not
lost if you naivgate and then come back
http://code.google.com/p/chromium/issues/detail?id=2636
SOLUTION:
this works for me. it's the same solution mentioned above.
disable-prompt-on-repost
here are more instructions
on p
Comment #49 on issue 2636 by johnywhy: Cache form data so edits are not
lost if you naivgate and then come back
http://code.google.com/p/chromium/issues/detail?id=2636
SOLUTION:
this works for me. it's the same solution mentioned above. here are more
instructions
on proper usage:
http://www.
Comment #56 on issue 2636 by andrew.john.peters: Cache form data so edits
are not lost if you naivgate and then come back
http://code.google.com/p/chromium/issues/detail?id=2636
Sorry guys, but you have really dropped the ball on this.
--
You received this message because you are listed in th
Comment #55 on issue 2636 by johnywhy: Cache form data so edits are not
lost if you naivgate and then come back
http://code.google.com/p/chromium/issues/detail?id=2636
hm, ok, weird, i deleted a post on this thread. then i closed the tab. then
i
reopened the tab with SHIFT-CTRL-T. then i cli
Comment #54 on issue 2636 by johnywhy: Cache form data so edits are not
lost if you naivgate and then come back
http://code.google.com/p/chromium/issues/detail?id=2636
hm, ok, weird, i deleted a post on this thread. then i closed the tab. then
i
reopened the tab with SHIFT-CTRL-T. then i cli
Comment #53 on issue 2636 by johnywhy: Cache form data so edits are not
lost if you naivgate and then come back
http://code.google.com/p/chromium/issues/detail?id=2636
hm, ok, weird, i deleted a post on this thread. then i closed the tab. then
i
reopened the tab with SHIFT-CTRL-T. then i cli
Comment #52 on issue 2636 by johnywhy: Cache form data so edits are not
lost if you naivgate and then come back
http://code.google.com/p/chromium/issues/detail?id=2636
Clicking 'back', it seems that NON-form pages actually ARE reloaded from
the server--
they don't just instantly pop into the
Comment #50 on issue 2636 by johnywhy: Cache form data so edits are not
lost if you naivgate and then come back
http://code.google.com/p/chromium/issues/detail?id=2636
that does not sound correct to me, because it is NOT the FORM we are going
back to
(with textboxes and user-entered text), b
Comment #48 on issue 2636 by scratched86: Cache form data so edits are not
lost if you naivgate and then come back
http://code.google.com/p/chromium/issues/detail?id=2636
@johnywhy
You can go back on non-form pages without reloading because the HTML & data
is stored
in cache to begin with.
Comment #47 on issue 2636 by johnywhy: Cache form data so edits are not
lost if you naivgate and then come back
http://code.google.com/p/chromium/issues/detail?id=2636
Google: why are you making this more complex than it needs to be? i can
go "back" on
NON-FORM pages without reloading. how?
Comment #46 on issue 2636 by johnywhy: Cache form data so edits are not
lost if you naivgate and then come back
http://code.google.com/p/chromium/issues/detail?id=2636
Google: why are you making this more complex than it needs to be? i can
go "back" on
NON-FORM pages without reloading? how?
Comment #45 on issue 2636 by mal7798: Cache form data so edits are not lost
if you naivgate and then come back
http://code.google.com/p/chromium/issues/detail?id=2636
I am just checking on the latest progress on this bug, since it has been
nearly a
month since the last post.
--
You received
Comment #44 on issue 2636 by kfastovets: Cache form data so edits are not
lost if you naivgate and then come back
http://code.google.com/p/chromium/issues/detail?id=2636
Yeah, horrible HORRIBLE function. I really hope they do something about
this soon
--
You received this message because yo
Updates:
Summary: Cache form data so edits are not lost if you naivgate and then
come back
Comment #43 on issue 2636 by m...@chromium.org: Cache form data so edits are
not lost if you naivgate and then come back
http://code.google.com/p/chromium/issues/detail?id=2636
Re-summarizing
35 matches
Mail list logo
