Your message dated Fri, 23 Sep 2011 11:56:15 +0300
with message-id <[email protected]>
and subject line Re: Bug#639620: chromium: fails to disable JavaScript when
opening
has caused the Debian Bug report #639620,
regarding chromium: fails to disable JavaScript when opening local HTML files
from the command line
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.)
--
639620: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639620
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: chromium
Version: 13.0.782.107~r94237-1
Severity: normal
Hi!
Thanks for maintaining Chromium in Debian!
I am currently a user of the Galeon web browser and I've recently
installed Chromium, in order to check whether it fits my needs as
my new primary browser...
While playing with Chromium, I noticed what appears to be a bug.
I have my preferences set with "Do not allow any site to run JavaScript"
checked and I haven't (yet) set any exceptions.
The JavaScript interpreter seems to be indeed disabled for all the
(remote) websites I visit (good!).
However, if I open a local HTML file (including embedded JavaScript code)
from the command line, as in:
$ chromium ~/my_html_file_with_js.html
chromium fails to disable JavaScript, until I refresh the page (which
may be too late, in some cases...).
I think that this is a bug, since, when I say "Do not allow any site to
run JavaScript", I really mean it, with no exceptions (unless I
explicitly set exceptions, of course!).
My impression is that Chromium reads my preferences too late, when
opening a file or URL given as a command-line argument, thus rendering
the page and starting the JavaScript interpreter before realizing that
I do not want the JavaScript interpreter to be enabled...
Or maybe the cause of the bug is completely different, I don't know for
sure.
How can this bug be fixed?
Thanks for your time.
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (800, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.0.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages chromium depends on:
ii chromium-inspector 13.0.782.107~r94237-1 page inspector for the chromium br
ii libasound2 1.0.24.1-2 shared library for ALSA applicatio
ii libbz2-1.0 1.0.5-6 high-quality block-sorting file co
ii libc6 2.13-16 Embedded GNU C Library: Shared lib
ii libcairo2 1.10.2-6.1 The Cairo 2D vector graphics libra
ii libcups2 1.4.8-2 Common UNIX Printing System(tm) -
ii libdbus-1-3 1.4.14-1 simple interprocess messaging syst
ii libdbus-glib-1-2 0.94-4 simple interprocess messaging syst
ii libevent-1.4-2 1.4.13-stable-1 An asynchronous event notification
ii libexpat1 2.0.1-7 XML parsing C library - runtime li
ii libflac8 1.2.1-5 Free Lossless Audio Codec - runtim
ii libfontconfig1 2.8.0-3 generic font configuration library
ii libfreetype6 2.4.6-1 FreeType 2 font engine, shared lib
ii libgcc1 1:4.6.1-4 GCC support library
ii libgconf2-4 2.32.4-1 GNOME configuration database syste
ii libgcrypt11 1.4.6-9 LGPL Crypto library - runtime libr
ii libgdk-pixbuf2.0-0 2.23.5-3 GDK Pixbuf library
ii libglib2.0-0 2.28.6-1 The GLib library of C routines
ii libgtk2.0-0 2.24.4-3 The GTK+ graphical user interface
ii libjpeg62 6b1-2 Independent JPEG Group's JPEG runt
ii libnspr4-0d 4.8.9-1 NetScape Portable Runtime Library
ii libnss3-1d 3.12.11-1 Network Security Service libraries
ii libpango1.0-0 1.28.4-1 Layout and rendering of internatio
ii libpng12-0 1.2.46-3 PNG library - runtime
ii libspeex1 1.2~rc1-1 The Speex codec runtime library
ii libstdc++6 4.6.1-4 GNU Standard C++ Library v3
ii libvpx0 0.9.7.p1-1 VP8 video codec (shared library)
ii libwebp0 0.1.2-1 Lossy compression of digital photo
ii libx11-6 2:1.4.4-1 X11 client-side library
ii libxext6 2:1.3.0-3 X11 miscellaneous extension librar
ii libxml2 2.7.8.dfsg-4 GNOME XML library
ii libxrender1 1:0.9.6-2 X Rendering Extension client libra
ii libxslt1.1 1.1.26-8 XSLT 1.0 processing library - runt
ii libxss1 1:1.2.1-2 X11 Screen Saver extension library
ii xdg-utils 1.1.0~rc1-2 desktop integration utilities from
ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime
chromium recommends no packages.
Versions of packages chromium suggests:
pn chromium-l10n <none> (no description available)
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi,
upstream replied that they can't reproduce the bug anymore and indeed it
does not occur anymore with 14.0.835.163~r101024-1. I do not know which
commit exactly fixed it.
Feel free to reopen if you still see the issue again with
14.0.835.163~r101024-1 or later version.
-Timo
--- End Message ---
