Bug 16382 - Should we have a NamedFlow.getRegionsByFlowRanges?
Summary: Should we have a NamedFlow.getRegionsByFlowRanges?
Alias: None
Product: CSS
Classification: Unclassified
Component: Regions (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Vincent Hardy
QA Contact: public-css-bugzilla
Whiteboard: cssom
Depends on:
Reported: 2012-03-15 00:18 UTC by Vincent Hardy
Modified: 2012-10-05 17:16 UTC (History)
3 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Vincent Hardy 2012-03-15 00:18:23 UTC
Feedback from Alex Chiculita, Adobe:

We have Region.getRegionFlowRanges that returns the Range[] array while there is no way to get all the regions of a specific range. For example, there's no NamedFlow.getRegionsByFragmentRange(). There's only NamedFlow.getRegionsByContentNode() . I'm not sure if it's needed, but it feels like it should go both ways.
Comment 1 Vincent Hardy 2012-03-15 14:05:52 UTC
use case proposed by Alex:

Could be used for detecting what regions are affected by the user selection. For example: the user selects some text and you might need to highlight the selected regions or show a contextual menu near the regions.
Comment 2 Alan Stearns 2012-10-05 17:16:46 UTC
Added as a possible future feature: