Issue 121281 in chromium: chrome-extension://invalid/ when going back in history to custom new tab page

[chro...@googlecode.com]

Status: Unconfirmed
Owner: ----
Labels: Type-Bug Pri-2 Area-Undefined OS-Windows

New issue 121281 by laboboL...@gmail.com: chrome-extension://invalid/ when
going back in history to custom new tab page
http://code.google.com/p/chromium/issues/detail?id=121281

Chrome Version : 18.0.1025.142
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
URLs (if applicable) :

What steps will reproduce the problem?
1.
On a clean chrome profile
Make sure you have navigated to "http://www.google.com/" at least once.
Load the extension i attached.
Open a new tab. If one doesn't automatically appear.
Click button "Start Index".
2.
Click on the tile "http://www.google.com/"
3.
Now navigate back, clicking the go back button to the left of omnibar.

What is the expected result?
That it returns to the new tab page, "chrome://newtab/"
aka "chrome-extension://mckjhbcodofhejmahhlpchbbolcnbcip/html/fauxbar.html"

What happens instead?

"This webpage is not available
The webpage at chrome-extension://invalid/ might be temporarily down or it
may have moved permanently to a new web address.
Error 2 (net::ERR_FAILED): Unknown error."

Please provide any additional information below. Attach a screenshot if
possible.

UserAgentString: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.19
(KHTML, like Gecko) Chrome/18.0.1025.142 Safari/535.19

I have tried to replicate this bug with the sample 'Blank new tab page'
without any success.
See attachments.

I can't trace nor debug it and i can't find anything wrong.
What i can say is that it worked perfectly fine in chrome v17.

Another strange thing:
I added a bookmark
to "chrome-extension://mckjhbcodofhejmahhlpchbbolcnbcip/html/fauxbar.html"
for debugging.
When that error happens i clicked the bookmark and the same thing happens
but not always.

If i click on the bookmark while on google.com i can also get that error
but not always.

Attachments:
Fauxbar.7z 203 KB
blank_ntp.7z 985 bytes

[chro...@googlecode.com]

Comment #2 on issue 121281 by laboboL...@gmail.com:

chrome-extension://invalid/ when going back in history to custom new tab
page
http://code.google.com/p/chromium/issues/detail?id=121281

In latest canary i finally get an error code:
Denying load of
chrome-extension://hibkhcnpkakjniplpfblaoikiggkopka/html/fauxbar.html.
Resources must be listed in the web_accessible_resources manifest key in
order to be loaded by pages outside the extension.
GET chrome-extension://invalid/

The is defiantly a bug. The back button should not count as the website
doing the navigation.

[chro...@googlecode.com]

Comment #1 on issue 121281 by laboboL...@gmail.com:

chrome-extension://invalid/ when going back in history to custom new tab
page
http://code.google.com/p/chromium/issues/detail?id=121281

[chro...@googlecode.com]

Updates:
Status: Untriaged
Cc: plud...@chromium.org
Labels: -Area-Undefined -OS-Windows Area-Internals OS-All
Feature-Extensions

Comment #3 on issue 121281 by mk...@chromium.org:

chrome-extension://invalid/ when going back in history to custom new tab
page
http://code.google.com/p/chromium/issues/detail?id=121281

+pludwig

[chro...@googlecode.com]

Updates:
Cc: mpcom...@chromium.org

Comment #4 on issue 121281 by plud...@chromium.org:

chrome-extension://invalid/ when going back in history to custom new tab
page
http://code.google.com/p/chromium/issues/detail?id=121281

(No comment was entered for this change.)

[chro...@googlecode.com]

Updates:
Status: Assigned
Owner: kal...@chromium.org

Comment #9 on issue 121281 by kal...@chromium.org:

chrome-extension://invalid/ when going back in history to custom new tab
page
http://code.google.com/p/chromium/issues/detail?id=121281

Thanks. My crappy 7z was flattening the directory hierarchy.

Ok, bug confirmed. I'll look into it.

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[chro...@googlecode.com]

Comment #11 on issue 121281 by laboboL...@gmail.com:

chrome-extension://invalid/ when going back in history to custom new tab
page
http://code.google.com/p/chromium/issues/detail?id=121281

This bug is old. I can't even remember I filed this bug. I still think it's
chromes fault though.

Remember I could not find any problem with the extension. I checked it
before submitting a bug report. The code looked fine to me at the time.

The 'blank_ntp' did reproduce the issue for me at the time.

You have the extension's source code and an added advantage of being able
to debug chrome. You should be able to answer that question better than I
ever could.

I stopped working on that problem soon after I filed the bug report.
Couldn't do anything more without a response and help from you (chrome
team) on the issue.

Perhaps the bug have become even more rare and complicated to reproduce?
Wouldn't be the first time that have happened.

[chro...@googlecode.com]

Comment #14 on issue 121281 by laboboL...@gmail.com:

chrome-extension://invalid/ when going back in history to custom new tab
page
http://code.google.com/p/chromium/issues/detail?id=121281

I hate to be a downer but you only have yourself to blame. Taking this long
to respond to the bug report.
Since you are a dev perhaps you can get hold of the old chrome version
(18.0.1025.142) and use that?
The minimal test case i provided a year ago worked than.

If only the bugs was dealt with in due time. The age brings more complexity
into the problem.
If this bug had been dealt with in due time it would not be as hard to
reproduce the bug.
A lot of things have change in chrome since then. Chrome is a fast moving
target.

Anyway i have checked the 'blank ntp' test myself and fauxbar extension.
Since it is a year ago i can't remember any of the details.
I managed to reproduce the error only once in fauxbar extension. The
extension gave me an error before i clicked the google thumbnail link.

"2013-02-25 03:17:56
1.2.5
_generated_background_page.html
js/common-1.js:319
Uncaught TypeError: undefined is not a function"

The problem is that this extension have not been updated since about that
time. It is outdated.
So this might not be related to the original issue.

In psychology it is very important to not promote and reward bad behavior.
Sorry, i will not make a new minimal test case for you.
You caused this increased problem so you have to fix it yourself.

My time is too limited and valuable to deal with such unnecessary time
wasting behavior.
Again sorry for the harshness but chrome team is getting on my nerves. The
time it takes to report a bug is wasted away on the lack of reward (fixing
the bug). Why do i even bother?

[chro...@googlecode.com]

Comment #17 on issue 121281 by dellagus...@gmail.com:

chrome-extension://invalid/ when going back in history to custom new tab
page

https://code.google.com/p/chromium/issues/detail?id=121281

I'm not sure I get the same issue, but I'm developing an extension for
which one of the use cases is to show a page with links to arbitrary
domains. There is no target, so the page will open in the same tab the
extension used to be. When I hit back, it goes to invalid
chrome-extension://invalid/, but I can see something flashing quickly in
the console when it happens.

At the end I'll probably change the target to always open it in a new tab.

[chro...@googlecode.com]

Updates:
Status: WontFix

Comment #19 on issue 121281 by roc...@chromium.org:

chrome-extension://invalid/ when going back in history to custom new tab
page

https://code.google.com/p/chromium/issues/detail?id=121281

I'm closing this because it hasn't been reproed and there's been no useful
activity for a long time. If someone encounters this in practice and can
provide a reduced test case, they should file a new bug.