High res image tiles not loaded correctly in slider for regular to panorama comparison
@oscarlorentzon is already working on this.
Since Jun 5, 2018.
Assessment
This issue has not been assessed yet.
Description
Basic information
MapillaryJS version: 2.12.0
System/Browser: All
Steps to Reproduce Behavior
- Create a viewer and initialize it with the slider:
var viewer = new Mapillary.Viewer(
"<element-id>",
"<client-id>",
"<regular-key>",
{
component: {
cover: false,
direction: false,
imagePlane: false,
sequence: false,
slider: { initialPosition: 1, keys: { foreground: '<regular-key>', background: '<pano-key>' } },
},
});
- Change to non-3D mode.
- Change the position of the slider so that the panorama is visible
- Zoom in.
Expected behavior
The high res tiles are loaded for the whole visible part of the panorama
Actual behavior
For some views only part of the panorama is updated with high res tiles and the rest stays in low res.
- Dominant language
- TypeScript
- Stars
- 519
- Forks
- 89
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 4
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from mapillary/mapillary-js
-
Missing tooltipsOpen
Difficulty 4/5 3-5 days Newbie friendliness 25/100
mapillary/mapillary-js#639 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
mapillary/mapillary-js#638 ·
-
Transition modeOpen
Difficulty 4/5 3-5 days Newbie friendliness 25/100
mapillary/mapillary-js#633 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
mapillary/mapillary-js#623 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
mapillary/mapillary-js#618 ·
All issues in mapillary/mapillary-js
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
wardian-app/Wardian#1603 ·
Maintainers usually reply within 1 day
-
Sign the pledgeOpen
Difficulty 1/5 Under an hour Newbie friendliness 85/100
input-output-hk/devx-updates#168 ·
Maintainers usually reply within 1 day
-
triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
github/docs#46222 · 1 comment ·
Maintainers usually reply within 1 day
-
agent-ready area: config area: skills type: chore upstream: brain-kit
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
dev experience frontend good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
cuttle-cards/cuttle#1403 ·
Maintainers usually reply within 1 day