AW: [Zope3-dev] a ConflictError grabbag: problems and solutions inzope.app.keyreference and zope.app.session
Hi Gary Betreff: [Zope3-dev] a ConflictError grabbag: problems and solutions inzope.app.keyreference and zope.app.session [...] I suppose a compromise would be to make a zope.minmax, and then have zope.app.session depend on it. That would be fine by me, but making a zope.* package requires agreement from interested parties. If I got this right, there is no there is no drawback, right? If so, it whould be better to have such improvments in zope in general. I guess having such improvments in optional packages whould end in not using it for none core developer and make zope more magicly as it allready is right now for beginners. Regards Roger Ineichen _ END OF MESSAGE Gary ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/dev%40projekt01.ch ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: [Checkins] SVN: z3c.form/trunk/src/z3c/form/ HTML element ids containing dots are not very good, because then the
On Jun 13, 2007, at 1:22 AM, Stephan Richter wrote: Hello Gary, I am sorry that it took me so long to respond, but I had to think about this problem for while and family is in town as well. Very much understood. On Sunday 03 June 2007 14:18, Gary Poster wrote: Hey. I've only had limited time to look at the new package(s) but what I've seen so far looks good. I hope to give it a whirl soon. You should! Definitely. You may want to check about the browser compatibility of having ids and names different. ... This example just shows me that the fix I checked in is correct. ... This checkin guarantees that the id and the name *never* share the same prefix namespace (ids use - and names . as separators) thus eliminating the problem alltogether. ... If you can send me a z3c.form-based form that does not behave correctly in IE6, I will be more than glad to revert this change and find another solution to the problem. I won't have time to do that anytime very soon. We encountered this problem again very recently actually. Here's a very small test case. Works correctly on Firefox, breaks on IE 7(!). Title: test bar (ok) foo (problem on IE 6 & 7) I understand your argument, but I'd be worried about being hosed anyway. Gary ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Re: [Checkins] SVN: z3c.form/trunk/src/z3c/form/ HTML element ids containing dots are not very good, because then the
The html is very lame, btw, including, as someone pointed out to me, a rather than a amp;. However, it shouldn't affect the demonstration. :-) Gary ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] a ConflictError grabbag: problems and solutions in zope.app.keyreference and zope.app.session
On Jun 14, 2007, at 4:45 PM, Dieter Maurer wrote: Gary Poster wrote at 2007-6-13 17:12 -0400: ... 2) The second problem is less serious, ... I doubt that this will help you much (we use such an implementation for many years and still see quite often session related conflicts). The reason: Sessions are often in a temporary storage and this has a very restricted history. For conflict resolution, a sufficiently large history is necessary (long enough to load the old state again). Very often, the available history is not long enough to resolve a conflict. Agreed with the general observation, such as with temporary storage; in our case, however, we do have enough history. Gary ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
AW: [Zope3-dev] Re: [Checkins] SVN: z3c.form/trunk/src/z3c/form/ HTMLelement ids containing dots are not very good, because then the
Hi Gary
Betreff: [Zope3-dev] Re: [Checkins] SVN:
z3c.form/trunk/src/z3c/form/ HTMLelement ids containing dots
are not very good, because then the
[...]
If you can send me a z3c.form-based form that does not behave
correctly in IE6, I will be more than glad to revert this
change and
find another solution to the problem.
I won't have time to do that anytime very soon. We
encountered this problem again very recently actually.
Here's a very small test case. Works correctly on Firefox,
breaks on IE 7(!).
I see, that's a known bug in IE.
input type=submit name=foo id=bar value=Bar /
input type=submit name=baz id=foo value=Foo /
Using the same id and name in different elements
ends in IE with getting the first element with that
id or name. This means getElementById('foo') will
return the first element found with the given
name=foo or id=foo.
The z3c.form framework avoids this perfectly because it
generates element names and ids like:
id=form-widgets-lastname name=form.widgets.lastname
This will make sure that we never generate equal names
and ids for all form elements.
Regards
Roger Ineichen
___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
