Added return to start feature in a form of a button. When clicked teleports back to the first panorama. Helps with finding the exact location and getting out stuck situations.
Added return to start feature in a form of a button. When clicked teleports back to the first panorama. Helps with finding the exact location and getting out stuck situations.
Then only left would change to leave space for the return to start button (and it would have a slightly bigger space).
I would modify this as follows:
```css
left: 65px;
```
```css
right: 20px;
```
Then only `left` would change to leave space for the return to start button (and it would have a slightly bigger space).

I didn't want to break the symmetry, and I was thinking putting buttons to the right as well. But if you prefer the button to be larger over the symmetry, it's fine by me.
I didn't want to break the symmetry, and I was thinking putting buttons to the right as well. But if you prefer the button to be larger over the symmetry, it's fine by me.
This semantically belongs to reset (after line 334) and resetRound (after line 360). Yes it will be some ugly code duplication but easier to find there and I plan to refactor this JS in the future.
This semantically belongs to `reset` (after line 334) and `resetRound` (after line 360). Yes it will be some ugly code duplication but easier to find there and I plan to refactor this JS in the future.
For semantical reasons I would use div instead of span because span is intended to be an inline element, however this a block element here.
#navigation.navigationItemdiv{
For semantical reasons I would use `div` instead of `span` because `span` is intended to be an inline element, however this a block element here.
```css
#navigation .navigationItem div {
```
I've realized I've left out the .navigationItem and that's why not the right div was selected. (I see now, that you wrote it correctly in your suggestion)
I've realized I've left out the .navigationItem and that's why not the right div was selected. (I see now, that you wrote it correctly in your suggestion)
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Added return to start feature in a form of a button. When clicked teleports back to the first panorama. Helps with finding the exact location and getting out stuck situations.
@@ -156,3 +189,3 @@#showGuessButtonContainer {position: absolute;left: 20px;left: 60px;I would modify this as follows:
Then only
leftwould change to leave space for the return to start button (and it would have a slightly bigger space).I didn't want to break the symmetry, and I was thinking putting buttons to the right as well. But if you prefer the button to be larger over the symmetry, it's fine by me.
If further buttons are planned, it is OK for me.
However I see you already changed the position, then I wouldn't change back.
@@ -152,0 +157,4 @@#navigation .navigationItem {margin-top: 10px;opacity: 70%;}Then it will feel like a link.
@@ -381,1 +381,4 @@Game.loadPano(Game.panoId, Game.pov);// needs to be set visible after the show guess map hid it in mobile viewdocument.getElementById("navigation").style.visibility = 'visible';This semantically belongs to
reset(after line 334) andresetRound(after line 360). Yes it will be some ugly code duplication but easier to find there and I plan to refactor this JS in the future.@@ -152,0 +163,4 @@opacity: 100%;}#navigation span {For semantical reasons I would use
divinstead ofspanbecausespanis intended to be an inline element, however this a block element here.I don't know why, but it breaks the visualization. I didn't see any difference in the CSS tree, when I tried it.
I've realized I've left out the .navigationItem and that's why not the right div was selected. (I see now, that you wrote it correctly in your suggestion)
@@ -61,1 +61,4 @@</div><div id="navigation"><div id="returnToStart" class="navigationItem"><span>https://gitea.e5tv.hu/esoko/mapguesser/pulls/26/files#issuecomment-197
Okay, it turned out for me that this PR is already closed :D Maybe this could still be merged independently or the changes could be merged with #27.