Timeline wont let me view it nor scroll past the mid 4 hundred thousands range.

closed
· Timelines ·
By Katherine_G_Evens on 09/05/2026
· Assigned to annapap9
· Not a Bug

My timeline wont scroll alll the way down it stops and wont go down any further in the mid 4 hundred thousand range, my species is very long lived so they have a massive time line, I am only on era 2 which ends in the year 9,704,413, and when I went to hit view to see if then I could at least see it popped up a error and to report the bug, I coppied the bug thingy here that it told me to copy: 46351592d9a244828c917b9d02febf7e

Steps to Reproduce

All I did was write my eras, I am only on the second era of my world, the first one lasts 704,412 years, but I cant even scroll all the way down to the end of that era alone because it just stops randomly and wont go lower randomly in the 4 hundred thousand range, my second era I added hoping it was a minor glitch lasts from 704,412 to 9,704,413, I only added those two and the descriptions I haven't even started on the historical events yet. I did copy paste my descriptions from my words file on the history.

Operating System

Windows

Browser

Microsoft Edge

Related Entity

The time line, it refuses to scroll down past the mid 4 hundred thousand section which makes it impossible to build the historic events I have written down.

History

katerinach @ 08 Sep, 2026 02:54:39 Developer
Assigned annapap9
annapap9 @ 09 Sep, 2026 11:34:35 Assignee

Hey there! Thanks for the detailed report! This is a known limitation with browsers when timelines get very large, due to their pixel limits.

For big timelines like yours (in years), we recommend using List Mode instead, as it avoids this limitation. If you’d like to see support for much larger timelines in the visual view, you’re also welcome to submit a feature request here: https://www.worldanvil.com/community/voting/ .

annapap9 @ 09 Sep, 2026 11:34:48 Assignee
annapap9 Added tag Not a Bug
Katherine_G_Evens @ 09 Sep, 2026 12:16:59

Oh ok, thank you. I kinda figured something like that was the cause, but I wanted to be sure just incase.

annapap9 @ 11 Sep, 2026 11:19:15 Assignee
set this bug to closed