| Summary: | [Table][TextSizeDetermination] Wrong itemHeight on the client in some cases | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [RT] RAP | Reporter: | Ivan Furnadjiev <ivan> | ||||
| Component: | RWT | Assignee: | Project Inbox <rap-inbox> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | neubauer | ||||
| Version: | unspecified | ||||||
| Target Milestone: | 1.5 M2 | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | sr141 | ||||||
| Attachments: |
|
||||||
|
Description
Ivan Furnadjiev
Two questions come to my mind: 1. Do we really need a PREPARE_UI_ROOT phase in RWTLifeCycle#PHASE_ORDER_SUBSEQUENT? 2. Do we need to handle "handleStartupProbeMeasurementResults" separately from "handleMeasurementResults"? Is handleStartupProbeMeasurementResults really needed? Created attachment 202075 [details]
Patch
After discussion with Frank, we agreed to introduce a boolean field ( isStartupProbeMeasurementPerformed ) in the MeasurementOperator that ensure that handleStartupProbeMeasurementResults is executed only once (in PREPARE_UI_ROOT phase of the first request only).
Applied patch to CVS HEAD. Applied patch to v14_Maintenance branch too. |