You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2020/07/06 18:57:00 UTC
[jira] [Commented] (SOLR-14422) Solr 8.5 Admin UI shows Angular
placeholders on first load / refresh
[ https://issues.apache.org/jira/browse/SOLR-14422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17152249#comment-17152249 ]
ASF subversion and git services commented on SOLR-14422:
--------------------------------------------------------
Commit 45573b9f1dbbc5bb46ca27a04ed5cf240c6da3b0 in lucene-solr's branch refs/heads/master from Eric Pugh
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=45573b9 ]
SOLR-14422 progressive render load main admin page (#1654)
* hide error message template until angular app has loaded
> Solr 8.5 Admin UI shows Angular placeholders on first load / refresh
> --------------------------------------------------------------------
>
> Key: SOLR-14422
> URL: https://issues.apache.org/jira/browse/SOLR-14422
> Project: Solr
> Issue Type: Bug
> Components: Admin UI
> Affects Versions: 8.5, 8.5.1, 8.5.2
> Reporter: Colvin Cowie
> Assignee: David Eric Pugh
> Priority: Minor
> Fix For: 8.6
>
> Attachments: SOLR-14422.patch, image-2020-04-21-14-51-18-923.png
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When loading / refreshing the Admin UI in 8.5.1, it briefly but _visibly_ shows a placeholder for the "SolrCore Initialization Failures" error message, with a lot of redness. It looks like there is a real problem. Obviously the message then disappears, and it can be ignored.
> However, if I was a first time user, it would not give me confidence that everything is okay. In a way, an error message that appears briefly then disappears before I can finish reading it is worse than one which just stays there.
>
> Here's a screenshot of what I mean !image-2020-04-21-14-51-18-923.png!
>
> I suspect that SOLR-14132 will have caused this
>
> From a (very) brief googling it seems like using the ng-cloak attribute is the right way to fix this, and it certainly seems to work for me. https://docs.angularjs.org/api/ng/directive/ngCloak
> I will attach a patch with it, but if someone who actually knows Angular etc has a better approach then please go for it
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org