Re: VOTE: set outputMarkupContainerClassName by default on in development mode

2009-02-06 Thread Matej Knopp
Vote closed. No -1 and 0s. -Matej 2009/2/6 Igor Vaynberg : > argh, this thread is about the vote. whether or not this causes > problems with the doctype is an orthogonal issue to whether or not > this is enabled by default. you can always disable it. that said, im > sure matej will fix the bug so

Re: VOTE: set outputMarkupContainerClassName by default on in development mode

2009-02-06 Thread Igor Vaynberg
argh, this thread is about the vote. whether or not this causes problems with the doctype is an orthogonal issue to whether or not this is enabled by default. you can always disable it. that said, im sure matej will fix the bug soon. but, please do try to keep the voting threads about the votes and

Re: VOTE: set outputMarkupContainerClassName by default on in development mode

2009-02-06 Thread Matej Knopp
Not really sure about it. Doctype is part of the markup stream. Easiest solution would be to put the page class on the very end of generated html, change would be trivial and it shouldn't break anything. -Matej On Fri, Feb 6, 2009 at 3:25 PM, Jan Loose wrote: > Hi, > > I tried to use setOutputMa

Re: VOTE: set outputMarkupContainerClassName by default on in development mode

2009-02-06 Thread Jan Loose
Hi, I tried to use setOutputMarkupContainerClassName() and this decorator creates the comment before and before tag . This is problem because IE7 recognize the document wrong (wrong render mode). Quirks mode in IE 7 can also be triggered when coding HTML 4.01 documents. Inserting a comme

Re: [VOTE] Release Apache Wicket 1.4 release candidate 2 (second try)

2009-02-06 Thread Frank Bille Jensen
The vote has passed with 6 +1 votes (binding), 1 +1 vote (binding) and no 0 and -1. I will upload to mirrors and announce when available. Thank you all for voting. Frank On 02/02/2009, at 20.33, Frank Bille Jensen wrote: Hey all, This is the second try on the 1.4-rc2. The first try was c