Status: Untriaged
Owner: dpra...@chromium.org
Labels: Type-Bug Pri-2 OS-All Area-Misc LayoutTests

New issue 24208 by dpra...@chromium.org: REGRESSION:  
LayoutTests\http\tests\navigation\post-goback1.html fails
http://code.google.com/p/chromium/issues/detail?id=24208

( Migrated from http://buganizer/issue?id=1204878 ).


darin on June 04 2008 03:00
(Assigned)
Summary
    REGRESSION: LayoutTests\http\tests\navigation\post-goback1.html fails
Component
    Chrome > Deprecated > WebKit > Glue
Reporter
    darin
Assignee
    darin
CC
    chrome-bugs
Type
    Bug
Priority
    P1
Severity
    S2
In prod
    false
Hotlist
    Cr__Rel_1.0
URLs affected
    <none>
Notes
REGRESSION: LayoutTests\http\tests\navigation\post-goback1.html fails

This started happening after my change to the way we handle error pages,
r43187.  That change modified the re-POST error page handling, so it is
perhaps unsurprising that this layout test is failing.  Unfortunately for
me, it doesn't fail on my machine.

For now it is marked as expected to fail.
mal on June 07 2008 00:38
(Assigned)
Priority
    P2
eseidel on June 24 2008 11:36
(Assigned)
Hotlist
    Cr__Rel_Future, Cr__Untriaged
Notes
This doesn't look like it should block us from shipping Beta.  Darin, if
you disagree, please pull this back into Cr_Beta.  Thanks.
darin on June 24 2008 11:38
(Assigned)
Hotlist
    Cr__Untriaged, Cr__Rel_1.0
Notes
I don't understand.  This is a regression of unknown degree that could be
serious and should be investigated for beta.
eseidel on June 24 2008 11:49
(Accepted)
Assignee
    eseidel
Notes
Darin and I discussed over chat.  I read his comments that it's possibly a
bot-only bug. In my experience real bugs are reported often (and loudly) by
users.  We have tons of regression test failures which are due to the
complexity of our setup, I expect that this may be one of those.

I will assign this to myself to investigate and confirm the severity of
this bug (or if it is even a bug).
eseidel on June 25 2008 08:51
(Accepted)
Notes
So somehow test_shell is failing to navigate back.  Not yet sure why.  This
is the diff:

---
c:\Projects\chrome\webkit\Release\layout-test-results\LayoutTests/http/tests/navigation/post-goback1-expected.txt
+++
c:\Projects\chrome\webkit\Release\layout-test-results\LayoutTests/http/tests/navigation/post-goback1-actual-win.txt
@@ -3,29 +3,15 @@
  layer at (0,0) size 800x600
   RenderBlock {HTML} at (0,0) size 800x600
     RenderBody {BODY} at (8,8) size 784x584
-      RenderText {#text} at (0,0) size 747x74
-        text run at (0,0) width 747: "This is just a minimal page that we
navigate in response to"
-        text run at (0,37) width 222: "an HTTP POST. "
-      RenderBR {BR} at (0,0) size 0x0
-      RenderBR {BR} at (0,74) size 0x37
-      RenderText {#text} at (0,111) size 763x111
-        text run at (0,111) width 743: "If the next line is empty after
the colon, it probably means"
-        text run at (0,148) width 178: "that we made "
-        text run at (178,148) width 585: "a mistake and requested this
page with a GET"
-        text run at (0,185) width 436: "with no query instead of a POST. "
-      RenderBR {BR} at (0,0) size 0x0
-      RenderBR {BR} at (0,222) size 0x37
-      RenderText {#text} at (0,259) size 709x37
-        text run at (0,259) width 709: "The first text field contained:
New form text from user "
-      RenderBR {BR} at (0,0) size 0x0
-      RenderText {#text} at (0,296) size 591x37
-        text run at (0,296) width 591: "This page was requested with an
HTTP POST"
+      RenderText {#text} at (0,0) size 722x74
+        text run at (0,0) width 722: "This is just a minimal page that we
navigate to as part of"
+        text run at (0,37) width 272: "testing back/forward."
       RenderText {#text} at (0,0) size 0x0
       RenderText {#text} at (0,0) size 0x0

  ============== Back Forward List ==============
         http://127.0.0.1:8000/navigation/post-goback1.html  **nav target**
         http://127.0.0.1:8000/navigation/resources/success200.html  **nav
target**
-curr->  http://127.0.0.1:8000/navigation/resources/postresult.pl  **nav
target**
-        http://127.0.0.1:8000/navigation/resources/otherpage.html  **nav
target**
+        http://127.0.0.1:8000/navigation/resources/postresult.pl  **nav
target**
+curr->  http://127.0.0.1:8000/navigation/resources/otherpage.html  **nav
target**
  ===============================================
eseidel on June 25 2008 09:41
(Accepted)
Notes
step 0: launch an httpd server (I used run-webkit-httpd, a script part of
the upstream WebKit checkout)


When I perform the same actions in chrome:

load:  http://127.0.0.1:8000/navigation/resources/success200.html
post to: http://127.0.0.1:8000/navigation/resources/postresult.pl
load: http://127.0.0.1:8000/navigation/resources/otherpage.html
hit back.

I get the (annoying) "form re-submission confirmation" page.


When I perform the above in test_shell, I get:

Error loading url: -400

And this is printed to the console:
ERROR: alias ISO-8859-8-I maps to ISO-8859-8-I already, but someone is
trying to make it map to ISO-8859-8
eseidel on June 25 2008 09:53
(Accepted)
Notes
This is a link to the change Darin mentioned as being possibly related:
https://svn.corp.google.com/v/chrome?view=rev&revision=43187
darin on June 25 2008 14:50
(Accepted)
Notes
OK, so this is just fallout from making the test_shell generate an error
page, like chrome, when navigating back to a form submission result.
Perhaps we should just rebaseline the test output and move on.
mal on July 14 2008 09:58
(Accepted)
Hotlist
    Cr__Rel_1.0
eseidel on July 18 2008 11:36
(Accepted)
Hotlist
    Cr__Rel_Future, Cr__Untriaged
Notes
I agree with Darin, but I can deal with the rebaselining post-beta,
post-merge when all many of our test results may change anyway.  Keeping
this bug around, but punting from Beta.


--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---

Reply via email to