On Sat, Jul 12, 2014 at 8:33 PM, Garret Wilson <gar...@globalmentor.com> wrote:
> On 7/11/2014 2:25 AM, Martin Grigorov wrote: > >> ... >> >> I recommend you to use Wicket 7.0.0-M2 for new development. >> It is quite stable! I use it for a personal applications. >> The benefit is that some of these things are improved there (e.g. p.1) and >> it is possible to make more radical changes. Changing the default behavior >> for p.2 will make Wicket's HTML not so *ugly* but will break many >> applications in production. No matter how ugly is the generated code I'll >> veto such change in 6.x. >> > > Martin, I note that getMarkupSettings().setDefaultBeforeDisabledLink(...) > et. al. are no longer available in Wicket 7.x. Does that mean that the HTML > modification I complained about for disabled links no longer occurs in > Wicket 7.x? > Take a look at https://cwiki.apache.org/confluence/display/WICKET/Migration+to+Wicket+7.0 Here we listed all changes introduced in 7.x The one about this particular change is https://cwiki.apache.org/confluence/display/WICKET/Migration+to+Wicket+7.0#MigrationtoWicket7.0-AbstractLinknolongeraltersitsmarkuptorenderitselfasdisabledWICKET-4904 Any feedback about improving the migration guide (making things more clear, etc) is very welcome! > > It seems also that by default a disabled link will merely remove the href, > which is fine. Do links in Wicket 7.x have any method hooks for modifying > the HTML, or do they rely on behaviors? (I hope the latter.) > > Lastly, is there any existing AttributeModifier behavior that adds an > attribute only if a component is disabled? (If not, that may be the perfect > thing for me to make my first contribution.) > > Best, > > Garret >
