[dx2] Browse opens file chooser instead of journal entry selector

[m_anish]

Testcase
1. Open Browse
2. Log into GMail
3. Compose a new message
4. Try to add an attachment
5. Instead of Journal entry selector, browse opens the file chooser dialog.

This issue exists on Browse 115/116 running on Dextrose-2, but doesn't seem to be present on jhbuild.

[alsroot]

That issue is absent in v119 on dx-2

[lucian]

Could you please upload a log of 115/116 running on dx-2? If it's fixed in 119, I'd like to know why.

[m_anish]

Replying to lucian:

Could you please upload a log of 115/116 running on dx-2? If it's fixed in 119, I'd like to know why.

Update (Test results Browse-119 on a XO-1; tests performed in the order as below):

(1) Objectchooser works correctly on wiki.sl.o
(2) Objectchooser works correctly on gmail.com | Basic HTML view
(3) Objectchooser does NOT work correctly on gmail.com | Standard view -> Pops up standard gnome filepicker instead of journal entry selector
(4) Doing (1) or (2) now popup the standard gnome file picker

I think I got a error/warning from sugar.graphics.objectchooser. Will search and paste log.

Since this exists in only some cases (as opposed to occurring everytime, I'm reducing severity to Minor)

[lucian]

I've managed to reproduce this bug.

I don't really have an idea what's going on, there doesn't seem to be anything relevant in the logs. It may be an obscure mozilla/xpcom bug.

[lucian]

I still can't figure out why this happens, but I have found an anomaly with Gmail's markup

<input id=":jg" type="file" name="f_gk5yiy530" class="LIODqc" size="50" tabindex="2" "="">

It sometimes appears as

<input id=":jg" type="file" name="f_gk5yiy530" class="LIODqc" size="50" tabindex="2" ">

in a file inspector.

Furthermore, putting this <input in a separate file doesn't reproduce the issue. This leads me to believe it has something to do with how Gmail manipulates the DOM in gecko/xulrunner.

Obviously Browse/xulrunner shouldn't choke on this, but Gmail should have the right markup anyway. I've reported the bug with Google.

[lucian]

Replying to lucian:

in a file inspector.

I meant in a DOM inspector (Webkits/Firebug).

[lucian]

Log of Browse running while this bug is reproduced.

[lucian]

Log of a regular run of Browse

[RafaelOrtiz]

Marking it as non-sugar, would be nice to have a link to the upstream bug.

[lucian]

I am not yet certain this is an upstream (i.e. mozilla/xulrunner/xpcom) bug.

About the Gmail bug reports, they're private. I can't get a link to it.

[m_anish]

Replying to lucian:

I am not yet certain this is an upstream (i.e. mozilla/xulrunner/xpcom) bug.

About the Gmail bug reports, they're private. I can't get a link to it.

For the time being, would including older (or newer) version of xulrunner that works well make sense?

For instance, I don't see the bug with up to date sugar-jhbuild running on a f13 machine.

[lucian]

Replying to m_anish:

Replying to lucian:

I am not yet certain this is an upstream (i.e. mozilla/xulrunner/xpcom) bug.

About the Gmail bug reports, they're private. I can't get a link to it.

For the time being, would including older (or newer) version of xulrunner that works well make sense?

For instance, I don't see the bug with up to date sugar-jhbuild running on a f13 machine.

If it doesn't happen on a newer xulrunner, that increases my confidence that the bug is there, not in Browse.

I don't really know if newer xulrunner is a feasible solution in the field.

[RafaelOrtiz]

Replying to lucian:

Replying to m_anish:

Replying to lucian:

I am not yet certain this is an upstream (i.e. mozilla/xulrunner/xpcom) bug.

About the Gmail bug reports, they're private. I can't get a link to it.

For the time being, would including older (or newer) version of xulrunner that works well make sense?

I'd say go for it, if we can fix the issue with a new xulrunner, might be work to try..we need to know wich version fits best.

For instance, I don't see the bug with up to date sugar-jhbuild running on a f13 machine.

If it doesn't happen on a newer xulrunner, that increases my confidence that the bug is there, not in Browse.

I don't really know if newer xulrunner is a feasible solution in the field.

[m_anish]

This issue does not exist on Browse running on the latest f14-11.x development builds. Might be worth exploring what versions of relevant packages are being used there and see if we can do something about it in f11.

Reopening.

[RafaelOrtiz]

I've investigated this, as anish said is not happening in F14

relevant packages versions.

xulrunner-1.9.2.10-1.fc14.1.i686
hulahop-0.7.1-3.fc14.i686

[RafaelOrtiz]

tested in sweets stable=sugar0.88 and testing=sugar0.92, not happening.

[RafaelOrtiz]

should be fixed on dx3 with the new version of xulrunner.

[m_anish]

[Keywords -= dx3] This doesn't happen on dx3.

[manuq]

For the relevant ticket for current Browse featuring WebKit, see #3411 . Shall we close this one as obsolete?

[m_anish]

+1 to closing this from my side (wontfix)