Add single click renderer for CommandButton

[jepsar]

See https://github.com/primefaces/primefaces/issues/2521

[jepsar]

@melloware do you have an idea how we could load the Javascript? I don't want to introduce a new component, just the renderer.

One option I see is to make it part of the documentation that you should load some (the PFE core?) Javascript if you want to use the renderer.

[Rapster]

Why don't you write JS code inline?

[melloware]

I don't know the spec but are we not allowed to use ResourceDependencies on Renderer's?

@ResourceDependencies({
        @ResourceDependency(library = "primefaces", name = "jquery/jquery.js"),
})

Because it would be nice just to have it in primefaces-extensions core.js so its not inline on the page and it gets compressed and cached.

[jepsar]

@Rapster I'd like to keep the outputted bytes to a minimum. But inline JS would be an option.

@melloware I think we are too late in the renderer to add resources.

[Rapster]

If you don't go on inline route then, you'll have to create a CommandButtonSingleClick component which only set a new @ResourceDependency

[melloware]

OK understood. that would be my preference vs inlining? @Rapster have any angst about that?

[melloware]

Plus it would allow for prototype overriding in JS if someone wanted to do something special or different in these methods as an added bonus.

[Rapster]

No, I have nothing against it but I think inline JS would be simpler: "PF(" + ((CommandButton) component).getWidgetVar() + ").enable();";

@jepsar Regarding confirmation, not sure why there is a special case on this, but you could use Confirmable#requiresConfirmation instead

[jepsar]

We don't need an exception on the buttons that require confirmation, but the confirmation buttons (the ones in the dialog).

[melloware]

I tested this morning with PrimeFaces.CSP = true and everything works great with this feature with Content Security Policy enabled.