Figure out a workable approach for cross-platform scroll position

NEW
Unassigned

Status

()

Firefox for Android
Reader View
3 years ago
3 years ago

People

(Reporter: rnewman, Unassigned)

Tracking

Trunk
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

3 years ago
Do we use word counts? Paragraph counts? Visual scroll position?

Do we rely on markup/DOM characteristics of Readability? If so, what do we do in the future if that changes?

Are we walking DOM text nodes, DOM paragraph nodes, or something else?

What can we do that's fairly stable across desktop, Android, and iOS?

This is a firm dependency for Bug 857990, and it also affects what we choose to do for word counts (in conjunction with a decision on reading time estimation -- Bug 959297, Bug 1106380).


If we decide that this is hard, or we don't care about either scroll position or word count/reading time yet, we can punt this. But we should be aware that this complicates future extension, and is a parity feature.

Updated

3 years ago
Blocks: 1154299
You need to log in before you can comment on or make changes to this bug.