Created attachment 1065315 [details] Screenshot Description of problem: It seems that save causes the Data Objects editor to refresh. If domain screen is expanded during the save, the current editor width is stored as maximum available and after hiding the domain screen the editor does not resize to full available space. Version-Release number of selected component (if applicable): 6.2.0.ER1 How reproducible: - Steps to Reproduce: 1. Open any Data Object. 2. Expand any domain screen. 3. Make a change in the data object and save it. 4. Hide domain screen. Actual results: Data Objects editor width does not increase after hiding domain screen. Expected results: Data Objects editor should resize to full available width. Additional info:
Happens with every editor. Another (simpler) way to reproduce: 1. Expand any domain screen. 2. Open any editor (e.g. guided rule, data object). 3. Hide domain screen. Result: Editor header bar (Title + Save, Delete, ...) is resized but the editor content is not.
I guess this should be some more general mechanism, likely related to uberfire
I've detected that the behavior was a side effect of the Lock mechanism that caused the editor to be reloaded after each save. It was reported and finally fixed by Christian in the following Uberfire commits: master: https://github.com/uberfire/uberfire/commit/82929783b8552da1c1fa9980f16a719ef3b7b423 0.7.x https://github.com/uberfire/uberfire/commit/d0d5504f86129026c784207c52d19dc410d5a1f1
Created attachment 1082757 [details] Behavioural problems of the data editor
BPMS 6.2.0.ER3 has the behavioural problems of the data editor. See screenshot.
I've re-tested it with the following results. 1) The resize effect initially reported in the BZ is fixed, or at least I've reproduced the steps 1,2,3, and the resizing is working as expected. 2) for the next reported issue "Behavioural problems of the data editor" I couldn't fined a reproducible sequence of steps. In my opinion issue reported originally is fixed, and I believe it's better to open a new one with the new "Behavioural problems of the data editor" described problem and if possible provide a reproducible sequence of steps.
One more comment about the re-sizing + docks, there are more commits in UF/UF-EXT that are complementary for fixing the described behavior. I've copy them here just for tracking. master: https://github.com/uberfire/uberfire/commit/4b33a9b679bd57a6706d612849a002d4f651bd91 https://github.com/uberfire/uberfire/commit/0c0cc548f119a877c9c10c4fcd78af2d4cf83204 https://github.com/uberfire/uberfire/commit/edb500cb84e630b486db01773f47c64c64df4025 https://github.com/uberfire/uberfire-extensions/commit/7fae846e8ef948fa29a1c0d32ee9ce06246dc2b6 https://github.com/uberfire/uberfire-extensions/commit/ec01a67c9e96a1992ce111294be147f89bb8f3a8 0.7.x: https://github.com/uberfire/uberfire-extensions/commit/f819209fb2a6340cfcbd5e82731b4e8e9537281a https://github.com/uberfire/uberfire-extensions/commit/665c21185909073100139d227d692667191f6451 https://github.com/uberfire/uberfire/commit/4a383572b3a52d126b162f932feffe9178f93813 https://github.com/uberfire/uberfire/commit/7827290a3f6d982fa59a6b140eaca34136e484a4 https://github.com/uberfire/uberfire/commit/74f6bb8efad314531012a76d9354773b28888f7d
Was re tested on 6.3.x (closest code used for the 6.2 GA branch) and it couldn't be reproduced. So I change status to modified so it can be retested, hopefully with next roll-up patch.
Yes, the original issue has been resolved. The problem described in comment 6 is tracked in a new bugzilla 1289536.