#22 — var:list doesn't work with safari
State | Resolved |
---|---|
Release: |
—
|
Area | Client side core plugins |
Issue type | Bug |
Severity | Medium |
Submitted by | (anonymous) |
Submitted on | 2007-12-01 |
Responsible | Balazs Ree |
Target release: |
—
|
Last modified on
2007-12-06
by
Balazs Ree
At least in the dnd-branch that I use on 2.5 it appears that with safari multiselect selects do not work with the :list affix. All other field types work but not selects. Jeroen tried to pinpoint it but couldn't find it so quickly.
So just for the record I mention it here.
Right now, our app is broken for Safari users.
So just for the record I mention it here.
Right now, our app is broken for Safari users.
- Steps to reproduce:
- create a multiselect select with a value:list and send the current form to the server. Then you will see that it will not end up in a list.
Added by
Danny Bloemendaal
on
2007-12-01 22:33
This issue was posted by me.
Added by
Balazs Ree
on
2007-12-02 10:11
Responsible manager:
(UNASSIGNED) → ree
Can you please post some more details?
The exact kss rule you use for the failed server action?
The server side method that you use to receive it?
The error you get? Any traceback? What do you get exactly in the form and what would be expected?
An exact html with which you get the problem? (or at least the form snippet)?
The best would be if you could make things like in a Demo, that way we could reproduce the problem easily. But if not, please just send every possible detail.
The exact kss rule you use for the failed server action?
The server side method that you use to receive it?
The error you get? Any traceback? What do you get exactly in the form and what would be expected?
An exact html with which you get the problem? (or at least the form snippet)?
The best would be if you could make things like in a Demo, that way we could reproduce the problem easily. But if not, please just send every possible detail.
Added by
Jeroen Vloothuis
on
2007-12-02 11:15
Issue state:
unconfirmed → open
The problem has nothing to do with :list fields since KSS does nothing special with them.
I updated the demo for this on the trunk. It shows that at least on Firefox this problem does not occur. It should not be simple to test using Safari if you install the demo and than go to the Parameter functions -> Forms section. The test to run is located at the bottom (output will be shown at the top).
I updated the demo for this on the trunk. It shows that at least on Firefox this problem does not occur. It should not be simple to test using Safari if you install the demo and than go to the Parameter functions -> Forms section. The test to run is located at the bottom (output will be shown at the top).
Added by
Danny Bloemendaal
on
2007-12-02 13:11
Well, nothing to do with kss? Jeroen, we both tried to make it work by altering the js stuff that comes with kss. So how can this not be related to kss? I know it works with firefox and we both saw that at some critical point, Safari returned a value somewhere that was not to be expected. It was this unexpected value that caused the breakage with multi-select selects. I understand that it is not related to :list but at least the code that prepares the form data is not working wel in this combination.
I think ;-)
I think ;-)
Added by
Danny Bloemendaal
on
2007-12-02 13:14
Oh..Jeroen, I think I misread your response ;-)
Nevermind then.. well, it's easy to test in Safari then but we both tried to make the buildout work on my machine (I'm a complete illiterate with buildout and eggs and stuff) but we didn't succeed (errors on import elementree eventhough it is installed) so I can't test the demo myself.
Nevermind then.. well, it's easy to test in Safari then but we both tried to make the buildout work on my machine (I'm a complete illiterate with buildout and eggs and stuff) but we didn't succeed (errors on import elementree eventhough it is installed) so I can't test the demo myself.
Added by
Balazs Ree
on
2007-12-06 13:51
Issue state:
open → in-progress
fixed on trunk
Added by
Balazs Ree
on
2007-12-06 13:51
Issue state:
in-progress → resolved