Closed pellmann closed 2 years ago
F0rce
commented
2 years ago Hello @pellmann,
This seems like an super odd issue, that I have never seen before. But let's try to sort it out.
Could you please tell me the Vaadin Version you are using? And if it is possible, could you please upload a simple vaadin starter that (hopefully) displays the problem, so I could investigate further (GitHub would be the ideal place therefore).
Thanks in advance, David
pellmann
commented
2 years ago Hi @F0rce, the Vaadin version is 14.8.1 - I will try to create something to reproduce, tomorrow. Thank you!
pellmann
commented
2 years ago Hi @F0rce, after I tried to reproduce with a new project and did not succeeded.. I rebuild my initial one with production mode on (which I think I have also tried before) and now I can not reproduce it any longer.. also not without production mode., good for me, but sorry for the wrong alarm.
F0rce
commented
2 years ago No worries, I am happy that the proplem was resolved (by itself).
Have a great time and thanks for the star, David
Describe the bug I used an other/old version of Ace for Vaadin Flow. Now I changed everything to Ace 1.3.4. It looks much more complete and is based in lit and I like it! The problem is, that in Chrome (96.0.4664.110 on OSX) and also in Brave (Version 1.34.80, Chromium: 97.0.4692.71 on OSX) the Component seems to not be really ready. It does not have syntax highlightning and also I noticed, it does not have a border.
It does not change anything if I call the Ace Menu (Cmd,) and change e.g. the syntax.
It is okay - with syntax highlightning and a border - after I switch views in my application. This switch sets components (parents of parents of the Ace Editor) unvisibel and visible again.
In Firefox the problem does not occur at all.
To Reproduce If needed I can try to create a Vaadin App to reproduce?
Screenshots Not working:
After switching views to an other and back:
Desktop (please complete the following information):