93457 - The Page Source are grayed-out in Asahi search result page

Status: VERIFIED WORKSFORME

(Core :: Internationalization, defect)

Description

[Yuying Long]

Build: 07-26 branch build on all platforms
Not reproduce on: IE and N4.7

Steps to reproduce:
1. Launch browser and go: http://www.asahi.com
2. Type a search word (doesn' matter with English or Japanese) in search field,
and click on Search.
3. Will brings up a search result page.
4. View | Page Source

Result:
This menu item is grayed-out.

I haven't see other pages(Yahoo-Ja, Netscape-Ja ...etc.) have the same result so
far.  Please reassign if it is not a i18n issue.

Comment 1

[Roy Yokoyama]

jbetak: can you take a look?
=== assigning to jbetak.

Comment 2

[[e-mail] (away - not reading bugmail)]

accepting...

Comment 3

[[e-mail] (away - not reading bugmail)]

hm, this is pretty odd and I believe it's not i18n-specific. Perhaps it's 
related to shifting window focus?

I'll talk to Yuying to see, how this affects us and possibly reassign.

Comment 4

[[e-mail] (away - not reading bugmail)]

ahh, I think we are getting closer - I´m seeing this with N6.1 RTM, but not with
a recent Mozilla trunk build. This might only happen on branch builds... Yuying,
could you please confirm this?

Comment 5

[Yuying Long]

You are right, on recent trunk build, the Page Source menu item is not grayed 
out as on Branch build, you can view the source.

However, the question now is, the page source will show a cgi page that only 
have one line that shows:
"Search service now is in maintenancing, please wait."

And with N4.7 and IE5.5, will display the page source of current search result.

Comment 6

[[e-mail] (away - not reading bugmail)]

the grayed out menu item and the source window content are two separate issues. 
And you are right - the source window should reflect the browser window 
contents, even for a cgi-generated page. I'll come up with a generic test case 
demonstrating this problem. If possible, we should file a separate bug for the 
source content problem. 

Also, do we know whether the source content problem is a regression or not? 
That would be really helpful, since I know for a fact that the view-source code 
has been messed with recently.

Comment 7

[Yuying Long]

Right they are seperate issues.

For the cotent problem, it is a regression - It was OK on 07-13 branch build, 
but grayed-out on 07-19 branch build.

Comment 8

[[e-mail] (away - not reading bugmail)]

Yuying, 

I have a simple test scenario: http://betak.net/cgiform.html

When you submit the form the page will say "Now you see me". When you attempt 
to view the page source with a recent Mozilla build the source will say "Now 
you don't". Both the page and its source should show identical content. Hope 
this helps as a test scenario. I'll also attach this to the bug, although I'm 
not sure, whether it will work or not.

Comment 9

[[e-mail] (away - not reading bugmail)]

Attachment: test form

Comment 10

[[e-mail] (away - not reading bugmail)]

cc'ing Frank and Harish - we might need to transfer this out of i18n, if this 
turns out to be a generic problem with viewing source of cgi-generated pages.

Comment 11

[Yuying Long]

jbetak is right, from view | Page source with his simple test case:
N6.1 - Now you don't
N4.7 and IE5.5 - Now you see me

It's turn to a generic problem which is different than the problem when original 
reported.  We might want to close this problem and open a seperate one for view 
cgi source issue.

Comment 12

[[e-mail] (away - not reading bugmail)]

Yuying,

would you like to resolve this or change into the generic version? I'm fine 
either way - the cgi test script I created sends "Now you see me", if there are 
any parameters sent with the request and "Now you don't", if there are no 
parameters sent. 

It appears to me that the view source window is making a separate new request 
w/o any parameters and hence it can receive a different response that the main 
browser window did. View source should not perform a new request and if it 
does, it needs to send the same request parameters to the server as the form in 
the main browser window did. This potentially affects all pages created in 
response to a POST request.

Comment 13

[[e-mail] (away - not reading bugmail)]

oh, how about the grayed out menu item? Should we keep this bug for that issue 
and open a new bug for the cgi view source problem?

Comment 14

[Yuying Long]

Grayed-out problem not existing on recent trunk build, so we might want to close
this bug for now.

Comment 15

[[e-mail] (away - not reading bugmail)]

OK then - would you please cc me on the new bug for cgi view source?

Comment 16

[Yuying Long]

Mark it as verified.

See bug 95149 for the cgi view source problem.