Cannot add comments on any bug report

Bug #32950 reported by Alex Muntada
4
Affects Status Importance Assigned to Milestone
Launchpad itself
Invalid
High
Unassigned

Bug Description

It's related to CSS and JavaScript, which are used to show the "+addmessage" form when pressing the "Add comment to this bug" on the page.

I'm using Firefox 1.5.0.1 on latest Dapper updates and I cannot add comments on any bug. The issue is related to CSS and JavaScript, which are used to show the "+addmessage" form when pressing the "Add comment to this bug" on the page.

I used the Firefox JavaScript console and found the following errors:

Error: Error in parsing value for property 'display'. Declaration dropped.
Source File: https://launchpad.net/@@/launchpad.css
Line: 10

Error: Error in parsing value for property 'display'. Declaration dropped.
Source File: https://launchpad.net/@@/launchpad.css
Line: 66

Error: icon.getAttribute("src") has no properties
Source File: https://launchpad.net/@@/launchpad.js
Line: 155

Tags: lp-bugs
Revision history for this message
Alex Muntada (alex.muntada) wrote :

I consider not being able to add comments to bug reports a big issue.

summary: + It's related to CSS and JavaScript, which are used to show the
+ "+addmessage" form when pressing the "Add comment to this bug" on the
+ page.
Revision history for this message
Diogo Matsubara (matsubara) wrote :

As a workaround you can use Malone email interface. You can find documentation on how to use it here:
https://wiki.launchpad.canonical.com/MaloneEmailInterfaceUserDoc

We'll investigate the problem, thanks for reporting it.

Revision history for this message
Alex Muntada (alex.muntada) wrote : Re: [Bug 32950] Cannot add comments on any bug report

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

* Diogo Matsubara <email address hidden>:
  [2006-03-02 19:54:40 -0000]

> As a workaround you can use Malone email interface.

Yes, I know. Just thought that other people may be suffering
the same issue, and wanted to let you know.

-----BEGIN PGP SIGNATURE-----

iD8DBQFEB2BMLdxCGS3zaBERAuaeAKCeNIfotyZzK42SBOMhYS/9uyNIigCgoyL/
YHSQP4mOpPRmt2hsSIdCr2M=
=BuEN
-----END PGP SIGNATURE-----

Revision history for this message
Brad Bollenbach (bradb) wrote :

On 26-Feb-06, at 11:41 AM, Alex Muntada wrote:

> Public bug reported:
> https://launchpad.net/malone/bugs/32950
>
> Affects: malone (upstream)
> Severity: Normal
> Priority: (none set)
> Status: Unconfirmed
>
> Description:
> I'm using Firefox 1.5.0.1 on latest Dapper updates and I cannot add
> comments on any bug. The issue is related to CSS and JavaScript, which
> are used to show the "+addmessage" form when pressing the "Add comment
> to this bug" on the page.
>
> I used the Firefox JavaScript console and found the following errors:
>
> Error: Error in parsing value for property 'display'. Declaration
> dropped.
> Source File: https://launchpad.net/@@/launchpad.css
> Line: 10
>
> Error: Error in parsing value for property 'display'. Declaration
> dropped.
> Source File: https://launchpad.net/@@/launchpad.css
> Line: 66
>
> Error: icon.getAttribute("src") has no properties
> Source File: https://launchpad.net/@@/launchpad.js
> Line: 155

I'm unable to reproduce this problem using the same FF on OS X.

Is it possible that you have an extension installed that might be
causing a problem?

  status needsinfo

Cheers,

--
Brad Bollenbach

Changed in malone:
status: Unconfirmed → Needs Info
Revision history for this message
Alex Muntada (alex.muntada) wrote :

It took me some time but I got I working right.
First, I removed all my Firefox extensions but
the bug was still happening, so I tried a more
aggressive approach: I entirely removed my
~/.mozilla and now it's working wonders!

Maybe there's something wrong on my preferences
being converted from Firefox version 1.0 to 1.5
after I upgraded from Breezy to Dapper.

Anyway, it wasn't LaunchPad fault.

Revision history for this message
Alex Muntada (alex.muntada) wrote :

By the way, I still see some errors on the JavaScript
console:

Error: Error in parsing value for property 'display'. Declaration dropped.
Source File: https://launchpad.net/@@/launchpad.css
Line: 10
Error: Error in parsing value for property 'display'. Declaration dropped.
Source File: https://launchpad.net/@@/launchpad.css
Line: 66

Revision history for this message
Brad Bollenbach (bradb) wrote :

Reporter confirms that it wasn't LP's fault.

Changed in malone:
status: Needs Info → Rejected
Revision history for this message
Matthew Paul Thomas (mpt) wrote :

"By the way, I still see some errors on the JavaScript console"

That's a bug in Firefox. Those "errors" are CSS2 values that Firefox doesn't support yet. They're nothing to do with JavaScript, so Firefox shouldn't be showing them in a JavaScript console.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.