Going to +bugs results in incorrect URL location

I cannot reproduce this at https://bugs.qastaging.launchpad.net/nova/+bugs with Opera 11.52, so some of our History handling changes may have fixed it as a side-effect. Can you still reproduce this?

On Fri, Dec 02, 2011 at 10:05:36PM -0000, Aaron Bentley wrote:
> I cannot reproduce this at
> https://bugs.qastaging.launchpad.net/nova/+bugs with Opera 11.52, so
> some of our History handling changes may have fixed it as a side-effect.
> Can you still reproduce this?

I joined the launchpad-beta-testers team on qastaging, but I still see
the old-style bug listing, so I can't test whether it's fixed or not.

Bjorn, can you try again? We have this marked as both Critical and Incomplete and it would be nice to change one or both of those.

While it may or may not be a regression, we've never made supporting Opera a HIGH or CRITICAL priority. We can downgrade to LOW as we sort out the issue.

Much as I'd like to fix it for Björn. :)

On Tue, Dec 13, 2011 at 04:31:23PM -0000, Matthew Revell wrote:
> Bjorn, can you try again? We have this marked as both Critical and
> Incomplete and it would be nice to change one or both of those.

I still see this on launchpad.net. If you want me to test it on
qastaging, you will have to explain how I make it so that I see the new
bug listing there.

On Tue, Dec 13, 2011 at 04:53:03PM -0000, Deryck Hodge wrote:
> While it may or may not be a regression, we've never made supporting
> Opera a HIGH or CRITICAL priority. We can downgrade to LOW as we sort
> out the issue.

It's certainly a regression, since I used to be able to search for bugs,
but can't anymore. While I understand that supporting Opera isn't a
priority, searching for bugs is such an essential feature, that it
should be possible in pretty much all browsers, no?

The fix should be simple, though. If you point me to the place where you
mock with the URL location, I might be able to provide you with a patch.
It should be as easy as using "" instead of null for some value.

To be clear, I think we should fix this. But I think it's low priority based on how we've always triaged Opera related bugs. I agree it's probably an easy fix, most like in our history handling code.

I can reproduce this on both production and qastaging now, using Opera 11.52

This also means pages like https://bugs.launchpad.net/~NICK are unbookmarkable:-(

The problem is still/also here for opera-next 12.00 (build 1301)

There is a detailed report with a fix on my.opera.com: http://my.opera.com/community/forums/topic.dml?id=1303132

Thanks for the work-around! I'll use it until to problem gets fixed for real

This needs to be fixed upstream, not in our code, but I'll make sure we get a bug against YUI and apply some form of the patched listed in the Opera bug.

Still here with Opera 12, but only reproduced by trying to reconfigure the bug tracker--config saved, but 404's on http://bigs.launchpad.net/+bugs/null

I cannot even search bug listings in Opera due to this bug. Workaround: use site:bugs.launchpad.net/[projectnamehere] on Google or DuckDuckGo.

See justification here why this is critical: https://bugs.launchpad.net/launchpad/+bug/62976/comments/9

I think with Opera 12.11, search works again, so this can be closed.

I removed my userscript that was supposed to fix this issue. And I can confirm it is indeed working again.