excess line feeds, bad html nesting, extra p's at end of rendered html,
I'm working on it atm - shall i commit for 4.1 ?
Personally I think it's non-critical. The default templates are not a "skin", they are what you get when you don't have
a skin. Judging from the fact that no-one has complained before, everyone either bases off Pattern skin or derives their own skin. I'd be surprised if anyone was using the default templates in anger (or Classic skin either).
But the final decision is Kenneth's.
I agree that it can be non-critical, but on the other hand, the default skin is unused because it has problems, so
- its low risk - no one can build on it in this state
- the sooner it can be built upon, the sooner we can improve and simplify skin development
Lavr - can you make a ruling for me
I can sway either way, but am working on it atm - i'll want to commit it soon after the 4.1 release, so i don't lose the work.
with the extra week Peter asked for to get more normal bugs fixed - we are OK but get the checkins done this week if possible.
i make an RC3 next weekend.
thanks. I've made an initial set of fixes that I have a unit test for using HTML::Lint
unfortuanatly, many CPAN based HTML validators are either broken, have woeful dependancies, or are just plan cruel - but I do want an automated test, otherwise we'll continue to lose.
I'll add the unit tests and skin development docco during the week, as my CssZenGarden
work goes along.
Strange observation. My tests pass if I test on a fresh svn checkout, but once I
there are failures again.
ok, main work done, if specific issues are found please raise a new Bug Item