No, it's a pretty reasonable approach. The question is what happens when Keycloak should be added to a product with much more strict requirements? It might not happen soon and the browser landscape is subject to change until then, but it remains a question to be answered at some point. If you build everything around cutting edge DOM and JS API's only supported by a small percentage of modern browsers you'd easily hit a wall.

/Heiko

On 24 Feb 2014, at 15:59, Bill Burke <bburke@redhat.com> wrote:

I'm asking because that's the approach we took with the Keycloak admin
console. Our user facing screens must be compatible with old browsers
where our admin console can rely on relatively modern Javascript APIs
and HTML support. Is this a bad approach to take?