Your message dated Wed, 13 Aug 2014 19:12:01 -0400
with message-id
<CANTw=mnclckye3l99ymvg3ncfqc-rbijc4g_a5ypyq7brqi...@mail.gmail.com>
and subject line Re: [Pkg-chromium-maint] Bug#717264: chromium: activating back
button does not redraw previous page
has caused the Debian Bug report #717264,
regarding chromium: activating back button does not redraw previous page
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.)
--
717264: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717264
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: chromium
Version: 25.0.1364.160-1
Severity: normal
Dear Maintainer,
I wrote my own microblog, which outputs a static HTML site from files in a Git
repository using the Bourne Shell and DJB redo. Then I did the following things:
1. Visit the home page of the blog <http://news.dieweltistgarnichtso.net/>
2. Go to the page for the first entry (link is the date string).
3. Activate the back button.
While the URL changed, no redraw occured. I expected the back button to not
only change the URL but also redraw the previously visited page.
Further testing gave that the expected behaviour occurs when the first page is
scrolled down a bit before navigating to the second page and navigating back.
A workaround is to activate the reload button.
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-3-686-pae (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages chromium depends on:
ii chromium-inspector 25.0.1364.160-1
ii gconf-service 3.2.5-1+build1
ii libasound2 1.0.27.1-1
ii libatk1.0-0 2.8.0-2
ii libbz2-1.0 1.0.6-4
ii libc6 2.17-3
ii libcairo2 1.12.14-4
ii libcups2 1.5.3-5
ii libdbus-1-3 1.6.12-1
ii libevent-2.0-5 2.0.21-stable-1
ii libexpat1 2.1.0-3
ii libflac8 1.3.0-1
ii libfontconfig1 2.10.2-2
ii libfreetype6 2.4.9-1.1
ii libgcc1 1:4.7.2-5
ii libgconf-2-4 3.2.5-1+build1
ii libgcrypt11 1.5.2-2
ii libgdk-pixbuf2.0-0 2.26.1-1
ii libglib2.0-0 2.36.3-3
ii libgnome-keyring0 3.4.1-1
ii libgtk2.0-0 2.24.10-2
ii libjpeg8 8d-1
ii libnspr4 2:4.10-1
ii libnss3 2:3.15-1
ii libnss3-1d 2:3.15-1
ii libpango1.0-0 1.30.0-1
ii libpulse0 2.0-6.1
ii libspeex1 1.2~rc1-7
ii libstdc++6 4.7.2-5
ii libudev0 175-7.2
ii libvpx1 1.2.0-2
ii libx11-6 2:1.6.0-1
ii libxcomposite1 1:0.4.4-1
ii libxext6 2:1.3.1-2+deb7u1
ii libxfixes3 1:5.0-4+deb7u1
ii libxml2 2.8.0+dfsg1-7+nmu1
ii libxrandr2 2:1.3.2-2+deb7u1
ii libxrender1 1:0.9.7-1+deb7u1
ii libxslt1.1 1.1.26-14.1
ii libxss1 1:1.2.2-1
ii xdg-utils 1.1.0~rc1+git20111210-7
chromium recommends no packages.
Versions of packages chromium suggests:
pn chromium-l10n <none>
-- debconf-show failed
--- End Message ---
--- Begin Message ---
Pages are intentionally cached by chromium for performance reasons, so
it is expected that a refresh is needed in this situation.
Best wishes,
Mike
--- End Message ---
