After delivering #349 via commit 29331b1 a regresion was found during release testing: maxwidth/maxheight constraints of the Dialog were calculated too big due to addition of the shadow. That addition should be done only in maximized mode. Moreover, the Dialog was not correctly resized in maximized mode when it had maxWidth/maxHeight set. Now that properties are ignored in maximized mode. Close #359.
Dialog can be now maximizable. If configured so, it will have a button to maximize/unmaximize next to the close button. It also reacts to the change of the data model property "maximized". That property takes precedence over center, xpos, ypos, width, height changes. When maximized, Dialog occupies the whole viewport and is not movable/resizable. After unmaximizing, it returns to the original position, size and other capabilities. Close #349. Close #358.
…es added to AT
Adds possibility to bind width and height for some of container-based widgets (Div, Dialog, Fieldset, TabPanel). The bound size is a subject to min/max size constraints for all of those widgets. This commit lifts the requirement for widgets to have width/height = -1 for min/max width/height to work. So this is backward-incompatible change in some way, but the behavior of width & maxwidth etc. when provided together was undefined earlier, so it should not have relied upon by anyone. Apart from the bindable width/height tests, this commit brings also a test case on static height constraints of the Dialog widget and their behavior when the contents od the Dialog change due to a refresh. Close #80. Close #347.
Makes it possible to increase (locally, per-user) no. of PhantomJS instances in Attester to parallelize the execution of the test suite when launched via 'npm run-script attester' (and 'npm test'). Type in the console e.g. npm config set ariatemplates:phantomjsInstances 4 to change the default to 4. Set it to ~= your processor's noOfCores * noOfThreads * 2 for max performance. E.g. on quad-core dual-threaded processor, set it to 4*2*2 = 16. Keep in mind that each thread consumes ~= 30-50 MB of RAM. This commit requires attester 1.0.2. Close #335. Close #337.
1. Allow usage of %1 %2 in assertEquals messages %1 and %2 are shortcuts for value1 and value2 params passed to %assertEquals and can be used as placeholders in the error message. This commit implements the feature (Assert.js) and changes some of the unit tests to use the new capability. 2. Fix the obvious issue with the error message of 'assertNotEquals'. 3. Write serialized versions of JSON entities in assertJsonEquals in case there's no default error message passed. Close #327. Close #328.
This commits brings a general-usage function to do recursive replacements in the AST given the replacements conditions, and adds two sample visitors that remove [$]descriptions from the beans and event definitions. The visitors are also capable to compute the number of bytes saved in the process (the number is displayed at the end of the build by a newly created Grunt task).
Html test contains two errors 1. disabled is a boolean attribute, so it's value should be 'disabled' 2. using border as style make testing IE painful, the returned value is "border-top/bottom/left/right" Using color reduces the problem but anyway the return value is 'COLOR: black' : mixed case and no semicolon
feat #309 vertical splitter implementation feat #309 vertical splitter implementation feat #309 vertical splitter implementation feat #309 vertical splitter implementation feat #309 vertical splitter implementation feat #309 vertical splitter implementation feat #309 vertical splitter implementation feat #309 vertical splitter implementation feat #309 vertical splitter implementation feat #309 vertical splitter implementation