Uploaded image for project: 'ZK'
  1. ZK
  2. ZK-1657

Window Maximize event does not contain correct window width or height

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Normal Normal
    • None
    • 6.5.0
    • Components
    • Security Level: Jimmy
    • ZK 6.5.0

      Test case:

      <zk xmlns:w="client">
      
      <window sizable="true" mode="overlapped" border="normal" title="test"
       	maximizable="true" minimizable="true" closable="true"
      	onMove="reportSize()" onMaximize="reportSize(event)" onSize='alert("onSize called")'>
      
      	<zscript>
      		 void reportSize() {
      			alert("window=" + self.width + " " + self.height);
      		 }
      		 void reportSize(Event evt) {
      			alert("win=" + evt.target + " window=" + evt.target.width + " " + evt.target.height + " event=" + evt.width + " " + evt.height);
      		 }
      	</zscript>
      	<borderlayout vflex="min" hflex="1"  style="background:magenta">
      		<north vflex="min" hflex="1" style="background:red" title="North">
      		</north>
      		<center vflex="min" hflex="1" style="background:green">
      		</center>
      		<south vflex="1" hflex="1" style="background:blue" title="South">
      		</south>
      	</borderlayout>
      </window>
      </zk>
      
      

      Steps to reproduce:
      1. Load the test page
      2. Maximize the window. You will see an alert reporting window width and height from event and also width and height from event object iteself.
      3. Restore the window
      Expected: You should see alert reporting window height and width from event object
      Actual: No width and height from event object.

      Note: If you resize the window before doing the maximize and then do step 2 and step 3 above then in step 3 you will see the restored correct window width and height in alert messagebox.

            jumperchen jumperchen
            ashishd ashishd
            Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: