i'm happy to report that all remaining issues have been fixed by
florian today. the reason that my findings were not immediately
reproducible, turned out to be because they were triggered by KSS
interactions, i.e. only if you previously had, for instance, performed
a copy operation andthen a workflow step. once fschulze found that out
he claims to have fixed several other issues of the same nature.
i've assigned the ticket to witsch, for lack of knowing anything
better. given that raphael has also looked at the plip i'd like to
suggest to 'officially' include 212 for 3.1: how are we going to go
about this? will we collect explicit votes from andi, martijn and danny?
On 15.02.2008, at 13:41, Raphael Ritz wrote:
Wichert Akkerman wrote:
Previously Tom Lazar wrote:
On Feb 14, 2008, at 1:57 PM, Florian Schulze wrote:
I can't reproduce any of these issues. I tried my exisiting
buildout and I made a fresh co of the buildout and ran buildout
with the option to get the newest version of everything.
well, given the fact that i indeed *can* reproduce these, chances
are, others will, too.
That's worrying. I would like to seem some succes/failure stories
from others -
FWIW: I just did a fresh buildout for 212 and tested a few
things in firefox (inline editing, calendar pagination, display
changes, workflow transitions, folder reordering, and running
the tests from test_ecmascripts ).
The only issue I've encountered is this one:
opera_is_broken is not defined
KupuSelectionTestCase()test_kupuhelpers.... (line 265)
registerTestCase(KupuSelectionTestCase(),
"kupu")unittestUtilities... (line 9)
opera_is_broken(this, 'testParentElementImg');
which Tom reported already.
Raphael
at the moment this feels like a big risk to me. Tom, can
you write a short step-by-step guide for reproducing the problems you
are seeing?
Wichert.
_______________________________________________
Framework-Team mailing list
[email protected]
http://lists.plone.org/mailman/listinfo/framework-team
_______________________________________________
Framework-Team mailing list
[email protected]
http://lists.plone.org/mailman/listinfo/framework-team
