Block Request for Inaccessible Widgets"

From Documentation
Line 22: Line 22:
 
Then, each time a desktop is created, an instance of <tt>InaccessibleWidgetBlockService</tt> is added to the desktop to block the requests from the inaccessible widgets.
 
Then, each time a desktop is created, an instance of <tt>InaccessibleWidgetBlockService</tt> is added to the desktop to block the requests from the inaccessible widgets.
  
In many cases, you just want to block particular events, not all events. For example, you want to receive <tt>onOpen</tt> when a <tt>menupopup</tt> is going to show up. Then, you can specify a library property called <javadoc>org.zkoss.zk.au.IWBS.events</javadoc> to control the behavior of <javadoc>InaccessibleWidgetBlockService</javadoc>. For example,
+
In many cases, you just want to block particular events, not all events. For example, you want to receive <tt>onOpen</tt> when a <tt>menupopup</tt> is going to show up. Then, you can specify a library property called <javadoc>org.zkoss.zk.au.IWBS.events</javadoc> to control the behavior of <javadoc>org.zkoss.zkmax.au.InaccessibleWidgetBlockService</javadoc>. For example,
  
 
<source lang="xml">
 
<source lang="xml">

Revision as of 09:52, 11 May 2012


DocumentationZK Developer's ReferenceSecurity TipsBlock Request for Inaccessible Widgets
Block Request for Inaccessible Widgets


Inaccessible widgets (such as disabled or invisible) can be accessed easily with a debugging tool running at the browser. For example, a hostile user can make an invisible button visible and then click on it to trigger unexpected actions. Thus, it is recommended not to create a widget if it is not supposedly accessible. For example, the first statement is safer than the second one in the following example:

<button unless="${accessible}"/>
<button visible="${accessible}"/>

Block with InaccessibleWidgetBlockService

[since 5.0.0]
[Enterprise Edition]

If you want to block a request for inaccessible widgets for the whole application or for a particular desktop, you can implement the org.zkoss.zk.au.AuService interface to filter out unwanted requests. ZK Enterprise Edition has provided a simple blocked called InaccessibleWidgetBlockService. To apply it to the whole application, just specify the following in WEB-INF/zk.xml as follows.

<listener>
	<listener-class>org.zkoss.zkmax.au.InaccessibleWidgetBlockService$DesktopInit</listener-class>
</listener>

Then, each time a desktop is created, an instance of InaccessibleWidgetBlockService is added to the desktop to block the requests from the inaccessible widgets.

In many cases, you just want to block particular events, not all events. For example, you want to receive onOpen when a menupopup is going to show up. Then, you can specify a library property called IWBS.events to control the behavior of InaccessibleWidgetBlockService. For example,

<library-property>
	<name>org.zkoss.zkmax.au.IWBS.events</name>
	<value>onClick,onChange,onSelect</value>
</library-property>

Implement Your Own Block

The implementation of AuService is straightforward. For example, the following example blocks only button and onClick:

public class MyBlockService implements org.zkoss.zk.au.AuService {
	public boolean service(AuRequest request, boolean everError) {
		final Component comp = request.getComponent();
		return (comp instanceof Button) && "onClick".equals(request.getCommand());
			//true means block
	}
}

Version History

Last Update : 2012/05/11


Version Date Content
     



Last Update : 2012/05/11

Copyright © Potix Corporation. This article is licensed under GNU Free Documentation License.