If displayedRegion is created with negative coordinates, you can run into odd bugs

[cmdcolin]

trafficstars

this scenario is really only able to create programmatically but it creates quite odd conditions. example: the region width (region.end-region.start)/bpPerPx doesn't correspond to the actual region rendered (which will actually have performed a Math.max(region.start,0))

[cmdcolin]

just for reference this was a session i saved from this that had this happen http://localhost:3000/?config=test_data%2Fvolvox%2Fconfig.json&session=share-SL4YknjuwX&password=AjnWD

[cmdcolin]

another one http://localhost:3000/?config=test_data%2Fvolvox%2Fconfig.json&session=share-qADNrxHkq7&password=IUMvh

you can see there is a gap where no coverage is plotted on snpcoverage, that is due to region width being calculated wrong here

again, not a very critical bug as you have to create these displayedRegions like this programmatically, not from the ui, but can cause surprising behavior

[cmdcolin]

there isn't an action item for this so i might close for now. there are just too many myriad places where sanity checks would be needed to make this actionable