Also, there are various gaps in the tree at times after clearing the search filter box.
I'll try to screenshot those.
It's ... weird .... perhaps you can make something out of it.
@NickGaens Just checked the demo app. It uses Domino-UI version 1.0.0-RC10. Doing a search inside the navigation tree works as expected. Please, can you check, that there is no additional coding from your side, that causes the error. As far as I can see fro your video, it looks like an element did get inivisible inside a tree item (that should be invisible) Please can you chek the generate code for that element.
@FrankHossfeld Did you run the demo app on your own pc? Or are you talking about https://demo.dominokit.org/home?
In the latter case how do you know this is RC10?
Cause the online demo states : Last build on : 2021-10-10T07:04:46Z
Which is before RC10 was released.
I cleared the .m2/org/dominokit directory and (so I thought) the browser cache, but somehow there must have been cached CSS files still present. The issues I showed above in the screenshot and the recording are no longer.
For our own css files, everytime we compile we append a different ?version=1234 to the <link href tags in the index.html file
But for those imported by domino we cannot do this
And we often have the problem when updating domino. That the olds css files are being used
These are not in my index.html
check the headers to be sure, i would be surprised if the client was the wrong one here
ok, so what i am describing is probably what IIS is doing - two quick suggestions:
- see if IIS can use e-tags instead, that way it is the hash of the file instead
- if not, when you unpack the war, touch all the files so that the date on them is the moment you did the most recent deploy
consider for example if you downgraded a deployment, rolled back to an older release
you wouldnt want the server to say "well you have the newer file, so keep that"
you want the server to know that the "old" file was deployed more recently
so you have to update the file's timestamp
(or use etags)
when this happens, look at the headers, i'll bet you a dollar that what i'm describing is happening
the simplest fix will be to touch each file when you unpack the war (either to tomcat or IIS)
not when you build the war, unless you can promise you deploy instantly after building and never ever rollback to old releases
do you see what i'm saying
Domino does not inject any css in the inndex page ..we expect you to manually build your html page and add links to those css files
ETag: "0eb32f0f914d71:0"
In tomcat
ETag: W/"40635-1615304174000"
Last-Modified: Tue, 09 Mar 2021 15:36:14 GMT
Last-Modified: Tue, 09 Mar 2021 15:36:14 GMT
Domino does not inject any css in the inndex page ..we expect you to manually build your html page and add links to those css files
hmmmm...
That is strange....
the last modified at least makes sense, that is a very old file, the user probably loaded the app since then