Your message dated Sun, 21 Sep 2014 12:02:01 -0400
with message-id
<CANTw=MPGHzdJ=UaJs=8cMkvsukxbTBjyDfAzM1o8e2U7q=g...@mail.gmail.com>
and subject line Re: [Pkg-chromium-maint] Bug#668125: chromium: opensearch
pageOffset defaults to 0 instead of 1, as per the spec
has caused the Debian Bug report #668125,
regarding chromium: opensearch pageOffset defaults to 0 instead of 1, as per
the spec
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
668125: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668125
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: chromium
Version: 18.0.1025.151~r130497-1
Severity: minor
Hi,
chromium's support for opensearch incorrectly sets pageOffset to 0 instead
of 1, as per the opensearch 1.1 draft 5. I found what appears to be an older
version of the source code and seems to default to 1, so I don't know what
happened there.
This is most likely an upstream issue and rather trivial to fix.
I've been told iceweasel does the right thing.
This is currently affecting www.d.o's search plugin, but I'm probably just
going to drop that parameter.
Cheers,
--
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net
--- End Message ---
--- Begin Message ---
> chromium's support for opensearch incorrectly sets pageOffset to 0 instead
> of 1, as per the opensearch 1.1 draft 5. I found what appears to be an older
> version of the source code and seems to default to 1, so I don't know what
> happened there.
> This is most likely an upstream issue and rather trivial to fix.
>From what I can tell, this works correctly now, tested opensearch in
various ways, but maybe not the right way to see the problem. If it's
still an issue, please submit an upstream bug report and reopen.
Best wishes,
Mike
--- End Message ---
