Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

URL segment loading indicator position in the wrong place #1625

Closed
clarkepaul opened this issue Sep 22, 2016 · 4 comments · Fixed by #1716
Closed

URL segment loading indicator position in the wrong place #1625

clarkepaul opened this issue Sep 22, 2016 · 4 comments · Fixed by #1716

Comments

@clarkepaul
Copy link
Contributor

clarkepaul commented Sep 22, 2016

Wasn't quick enough to get a screenshot of it but edit the page name and click outside of the input to see indicator.
pasted_image_22_09_16__3_20_pm

@hoKRa1
Copy link
Contributor

hoKRa1 commented Jan 17, 2017

Hi Paul,

Just wondering if you had any visual indicators that could perhaps show where the loading indicator is supposed to be positioned.

Thanks

@clarkepaul
Copy link
Contributor Author

It would be okay to use the existing gif for this issue I would think. I will update all the icons to font-icons at some stage but we don't have a spinning font-icon loading indicator yet.

Old loading gif is here cms/client/dist/images/loading.gif
And it used to appear just before the URL/input I think.
pasted_image_18_01_17__1_00_pm

@chillu
Copy link
Member

chillu commented Apr 19, 2017

Pointer for how to fix this: This is in admin/pages, and Entwine logic (not React). Check SiteTreeURLSegmentField.js

@clarkepaul
Copy link
Contributor Author

Still an issue and now smaller screen sizes need to also be considered.

tractorcow pushed a commit to hoKRa1/silverstripe-cms that referenced this issue Aug 24, 2017
tractorcow pushed a commit to hoKRa1/silverstripe-cms that referenced this issue Aug 24, 2017
flamerohr added a commit that referenced this issue Aug 24, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants