[Bug 16382] New: Should we have a NamedFlow.getRegionsByFlowRanges?

• From: <bugzilla@jessica.w3.org>
• Date: Thu, 15 Mar 2012 00:18:24 +0000
• To: public-css-bugzilla@w3.org
• Message-ID: <bug-16382-5148@http.www.w3.org/Bugs/Public/>

https://www.w3.org/Bugs/Public/show_bug.cgi?id=16382

           Summary: Should we have a NamedFlow.getRegionsByFlowRanges?
           Product: CSS
           Version: unspecified
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Regions
        AssignedTo: vhardy@adobe.com
        ReportedBy: vhardy@adobe.com
         QAContact: public-css-bugzilla@w3.org
                CC: eoconnor@apple.com


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.
===

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Thursday, 15 March 2012 00:18:26 UTC