FLUID-2495: RangeAnnotator options should not be top-level Pager options

Metadata

Source
FLUID-2495
Type
Bug
Priority
Major
Status
Closed
Resolution
Cannot Reproduce
Assignee
N/A
Reporter
Anastasia Cheetham
Created
2009-04-02T17:03:15.000-0400
Updated
2017-01-16T09:54:32.033-0500
Versions
  1. 1.0
  2. 1.1
  3. 1.1.1
  4. 1.1.2
  5. 1.2
  6. 1.3
  7. 1.3.1
  8. 1.4
Fixed Versions
N/A
Component
  1. Pager

Description

Currently, the Pager supports three top-level options that are used to configure its RangeAnnotator subcomponent:
annotateColumnRange
tooltipDelay
tooltipId

Since these options are specifically for configuring the subcomponent, they should be defined as options to the subcomponent itself, and passed in through the subcomponent definition object.

Comments

  • Anastasia Cheetham commented 2011-10-14T15:15:53.764-0400

    As of 1.4, annotateColumnRange is still a top level option. The other two no longer are.

  • Justin Obara commented 2014-07-09T10:09:16.431-0400

    Antranig Basman do you have thoughts on this issue?

  • Justin Obara commented 2017-01-16T09:54:32.029-0500

    It seems that there has been some refactoring to the pager component which changes the implementation related to the rangeAnnotator. There is still a fluid.pagedTable.rangeAnnotator grade; however, this grade doesn't appear to be used at all. It seems to be used more like a call to fluid.registerNamespace with a method in its namespace used as a listener.