RE: Re: RE: Re: RE: Re: Separate portlet app deploy. OrbeonPortletXFormFilter getContent() ()

Posted by Stian Sigvartsen on
URL: https://discuss.orbeon.com/RE-Re-RE-Re-RE-Re-Separate-portlet-app-deploy-OrbeonPortletXFormFilter-getContent-tp3175418.html

Hi Eric
Is the xxforms:noscript property going to remain unavailable in CE
versions 3.8+?
Also, is it unavailable for the Form Runner also in CE versions 3.8+?

We're a UK local authority so accessibility is very important feature
for ourselves.  If Orbeon forms (or XForms more generally) becomes a key
component for creating eForms and rich forms for applications/portlets
then of course we would look to get it supported via the PE, but until
such time this is going to be difficult I suspect.

-Stian

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Erik
Bruchez
Sent: 14 October 2010 02:57
To: [hidden email]
Subject: [ops-users] Re: RE: Re: RE: Re: Separate portlet app deploy.
OrbeonPortletXFormFilter getContent() ()


Stian,

Great to hear you have made progress! I voted on the Liferay post,
although it probably makes no difference.

The JavaScript-free mode is called "Noscript mode". It is not
automatically enabled based on what's in the browser: you have to
enable it with xxforms:noscript="true" on your XForms model.

Note that this feature only works in Orbeon Forms PE as of 3.8.

Form Runner supports this too and presents an "Accessible Version"
link at the top of forms so you can switch to that version.

-Erik


--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws