SolidDigital/magic-focus-finder issues and pull requests

#34 - only pull in used lodash methods for 60k of savings :)

Pull Request - State: closed - Opened by lukechinworth over 7 years ago - 7 comments

#33 - mouse support

Pull Request - State: open - Opened by salexch over 8 years ago - 11 comments

#32 - fix watch attribute change

Pull Request - State: closed - Opened by salexch over 8 years ago - 15 comments

#31 - If element uses an azimuth or distance weight for directional override, ignore line of sight selection.

Issue - State: closed - Opened by Duder-onomy over 9 years ago

#30 - Should calculate the position of dynamic elements during the finding algorithm and not when there is a move event.

Issue - State: closed - Opened by Duder-onomy over 9 years ago

#29 - `Document.createEvent` is deprecated, use `CustomEvent()` instead.

Issue - State: open - Opened by Duder-onomy over 9 years ago

#28 - Direction should have precedence

Issue - State: closed - Opened by dobbobolina over 9 years ago - 4 comments

#27 - Create Example using the 'useRealFocus' as false config.

Issue - State: open - Opened by Duder-onomy over 9 years ago

#26 - Should NEVER give focus to an item you cannot see.

Issue - State: closed - Opened by Duder-onomy over 9 years ago - 1 comment

#25 - Elements should be able to override the focus algo per direction

Issue - State: closed - Opened by Duder-onomy over 9 years ago

#24 - Configurable Focus Algorithm should accept multiple algorithms.

Issue - State: open - Opened by Duder-onomy over 9 years ago

#23 - Changing the 'container' does not remove domObservers from the old container.

Issue - State: open - Opened by Duder-onomy over 9 years ago

#22 - Should traverse child nodes when nodes are added from mutation and DOM observers.

Issue - State: closed - Opened by Duder-onomy over 9 years ago

#21 - Should never give focus to hidden, or display:none elements

Issue - State: closed - Opened by Duder-onomy over 9 years ago

#20 - Should support focus wrapping.

Issue - State: open - Opened by Duder-onomy over 9 years ago

#19 - Should not use collection with keymap, keycode should be the `key` and `value` should be the direction.

Issue - State: closed - Opened by Duder-onomy over 9 years ago

#18 - if focus override direction === 'skip' then do not move in that direction at all.

Issue - State: closed - Opened by Duder-onomy over 9 years ago

#17 - Initially added "focused" class is no longer being respected

Issue - State: open - Opened by pajtai over 9 years ago
Labels: bug

#16 - Should be able to send an element reference in as the container instead of a selector.

Issue - State: closed - Opened by Duder-onomy over 9 years ago - 1 comment

#15 - Example page showcasing the capture-focus feature. Add new elements to the DOM and have them capture focus.

Issue - State: open - Opened by Duder-onomy over 9 years ago

#14 - Example page with elements whose position is dynamic.

Issue - State: open - Opened by Duder-onomy over 9 years ago

#13 - Example page similar to a tv keyboard to enter email address etc.

Issue - State: open - Opened by Duder-onomy over 9 years ago

#12 - Decouple find closest algorithm.

Issue - State: open - Opened by Duder-onomy over 9 years ago

#11 - Private is a reserved word on Samsung TVs.

Issue - State: closed - Opened by Duder-onomy over 9 years ago

#10 - use phantom.js instead of zombie. Zombie intentionally returns zeros for element positioning. And thats what we need to test.

Issue - State: closed - Opened by Duder-onomy over 9 years ago - 1 comment

#9 - should not be able to call start more than once.

Issue - State: open - Opened by Duder-onomy over 9 years ago

#8 - new MouseEvent() is not supported in shitty browsers. Shim it for LG tv, or use new CustomEvent();

Issue - State: closed - Opened by Duder-onomy over 9 years ago - 1 comment

#7 - Create example site.

Issue - State: closed - Opened by Duder-onomy over 9 years ago

#6 - Finish Documentation.

Issue - State: open - Opened by Duder-onomy over 9 years ago

#5 - Implement a destroy method.

Issue - State: closed - Opened by Duder-onomy over 9 years ago - 1 comment

#4 - Capture Focus override

Issue - State: closed - Opened by Duder-onomy over 9 years ago

#3 - Focus should never be lost.

Issue - State: closed - Opened by Duder-onomy over 9 years ago

#2 - update the mutation observer to remove elements from the knownElements collection as they leave the DOM.

Issue - State: closed - Opened by Duder-onomy over 9 years ago

#1 - Use Lodash AMD so that it only requires the modules it needs.

Issue - State: closed - Opened by Duder-onomy over 9 years ago - 1 comment

Ecosyste.ms: Issues

GitHub / SolidDigital/magic-focus-finder issues and pull requests

#34 - only pull in used lodash methods for 60k of savings :)

#33 - mouse support

#32 - fix watch attribute change

#31 - If element uses an azimuth or distance weight for directional override, ignore line of sight selection.

#30 - Should calculate the position of dynamic elements during the finding algorithm and not when there is a move event.

#29 - `Document.createEvent` is deprecated, use `CustomEvent()` instead.

#28 - Direction should have precedence

#27 - Create Example using the 'useRealFocus' as false config.

#26 - Should NEVER give focus to an item you cannot see.

#25 - Elements should be able to override the focus algo per direction

#24 - Configurable Focus Algorithm should accept multiple algorithms.

#23 - Changing the 'container' does not remove domObservers from the old container.

#22 - Should traverse child nodes when nodes are added from mutation and DOM observers.

#21 - Should never give focus to hidden, or display:none elements

#20 - Should support focus wrapping.

#19 - Should not use collection with keymap, keycode should be the `key` and `value` should be the direction.

#18 - if focus override direction === 'skip' then do not move in that direction at all.

#17 - Initially added "focused" class is no longer being respected

#16 - Should be able to send an element reference in as the container instead of a selector.

#15 - Example page showcasing the capture-focus feature. Add new elements to the DOM and have them capture focus.

#14 - Example page with elements whose position is dynamic.

#13 - Example page similar to a tv keyboard to enter email address etc.

#12 - Decouple find closest algorithm.

#11 - Private is a reserved word on Samsung TVs.

#10 - use phantom.js instead of zombie. Zombie intentionally returns zeros for element positioning. And thats what we need to test.

#9 - should not be able to call start more than once.

#8 - new MouseEvent() is not supported in shitty browsers. Shim it for LG tv, or use new CustomEvent();

#7 - Create example site.

#6 - Finish Documentation.

#5 - Implement a destroy method.

#4 - Capture Focus override

#3 - Focus should never be lost.

#2 - update the mutation observer to remove elements from the knownElements collection as they leave the DOM.

#1 - Use Lodash AMD so that it only requires the modules it needs.