Metadata
- Source
- FLUID-6779
- Type
- Bug
- Priority
- Major
- Status
- Open
- Resolution
- N/A
- Assignee
- Antranig Basman
- Reporter
- Antranig Basman
- Created
2024-04-23T11:42:36.816-0400 - Updated
2024-04-23T11:42:37.231-0400 - Versions
-
- 4.6
- Fixed Versions
- N/A
- Component
-
- Framework
Description
The DOM binder’s EL resolution (implemented through the weird “resolvePathSegment()” hack) has the priorities the wrong way round - for example, a selector named “clear” has its results hidden by the DOM binder method named “clear” when resolved via an expression like {that}.dom.clear
There must be a further bug since the implementation of fluid.model.resolvePathSegment in Fluid.js line 1126 does appear to give priority to the return value of resolvePathSegment.