when in the Magnolia UI a click/double click on a node provokes a redraw of the UI. That wouldn't be bad if after the click the focus would still be the same but instead your are being thrown to a random node as the focus. Its frustrating to work with because with a big structure like we have, for every click you need to scroll and look again for the node you want to work with.
I googled extensively but have found no clue how to fix this behaviour.
It happens in Chrome 56.0.2924.87 as well as in Firefox 52.0.2 (64-Bit)
Any idea would be welcomed, this is really annoying.
Best wishes,
Chris
I assume you hit to https://jira.magnolia-cms.com/browse/MGNLUI-4084,
this has been fixed since 5.5.2. Please try to update and see if that works for you.
If unfortunately that's not the case, please feel free to report it to Magnolia.
Cheers,
Related
Or is it just me. My own project using tracked hands was working fine yesterday, then today the hands stopped working. After reversing changes since then and still failing, I rechecked one example that was working correctly on Jan. 20: https://aframe.io/aframe/examples/showcase/hand-tracking/ - now, it is not showing hands, or allowing the controls to be used. The hands do show outside of VR when the controller is set down or inside VR when the Menu is invoked. On my device, Hand tracking is on, and the experimental 'WebXR experiences with hand and joint tracking', in chrome://flags, is enabled, both of which I believe are required and were enabled when this was working previously. Turned everything off and on several times, removed batteries, re-paired controllers and did a factory reset of the headset, all per instructions from Oculus support - to no avail. They said they will contact me after asking for invoice info. However it would be good to know if this is some other issue. Can anyone confirm that the above example is, or is not, failing in Quest 2, or is there some other update or change that might be affecting this?
Same for me on Quest 1.
The Three.js examples with Handtracking are working.
Try https://threejs.org/examples/?q=webxr#webxr_vr_handinput_cubes
I recognized that the oculus browser now says "...wants to enter with handtracking" So something changed in the oculus browser that has to be updated in the jslibraries.
But that will change again with chromium 88
I am on oculus browser 13.4.0.3.15 with chromium 87.0.4280
There must have been one cause I had the same problem.
Found this seemingly related fix in the A-Frame code, mostly bone name changes.
And that's what helped me.
<script src="https://aframe.io/releases/1.2.0/aframe.min.js"></script>
I was calling for a previous version of the framework.
I have a website that I designed based on the "Holy Grail" layout described in this A List Apart post. A recent Chrome update broke it. You can see the results on the example page for the article (I also made it into a fiddle). Open it in Firefox to see what it should like and in Chrome to see what's happening now.
I realize that this technique is super dated, and I have plans in place to redesign it with Flexbox. But, that will take time, and I was hoping to get it working again quickly in the meantime while I work on a redesign. You can read more about LayoutNG on this page.
Does anyone know any tips and tricks to fix this? Is there a Chrome bug already open that I can follow?
Update: I decided to test it in Canary (v79), and the layout works perfectly there. It's still broken in Beta though (v78). So, I could wait until the current Canary gets released, but that won't be until December according to current estimates. So, I would still like to find a quick fix between now and then if one is available.
Here's some code to make SO happy:
SO won't let me post a link to jsFiddle without code...smart
It turned out to not be that hard to reimplement the layout with Flexbox. So, I just did some good old fashioned user agent sniffing to detect broken Chrome versions and load a small CSS snippet to override the appropriate styles.
Hi I have quite an unusual query. I have made a small JavaFX program and am very proud of the results. However I recently noticed a bug I can't seem to rap my head around. I can't recreate it either and do not have a screen shot of it unfortunately. However you can see a screenshot of the general program below in the state that triggered the problems.
I was running my program like normal and gave it quite a large load to handle (a lot of gradients as seen below). Then what happened was that in any TextField I typed in all edited text became a completely white rectangle and if I tried to update the image preview to the right it also turned white. If I let the program be in this white state for about ten seconds everything would load back in and behave like normal until I went to edit anything again.
It happened with any StyleSheet I loaded and as mentioned I cannot seem to recreate it. So my question is this. Is this a known error that can occur if you configure your scene in the wrong way (or something similar) or have I just managed to screw things up in general? The source code is quite long and I have absolutely no Idea where the problem may lie so I won't post any if you don't feel like a specific part may be interesting.
I am also aware that this type of general question is not really liked here so sorry about that. If you can suggest another more suitable forum I would be more than happy to move my question there.
//Thanks for any help.
EDIT: I finally managed to get a screen shot of the bug. I am not having high hopes that anyone is going to answer this though...
I'm developing a MEAN stack application. I have a very rare glitch that makes my site unusable.
I have make video to illustrate what is happening.
Things to take notes about:
The glitch is solved when I hover over the tab name, or when I move to another chrome tab and I return here.
Could you tell me if you have seen something like this before?
Thanks in advance for your answers and your time.
Here is the video link: https://drive.google.com/file/d/0B0QWPtcmBoNIaVVGMjhubnhQZVU/view?usp=sharing
I am experiencing the following (strange) bug:
When my site is seen on iPhone 4 (haven't tested on 5), an extra "Search web" bar appears when scrolling up and down. It slows down the browsing dramatically. It happens on both Safari and Chrome. It doesn't happen on other sites on the same device (so it is not a problem with the phone itself or its browse).
I cannot find any similar reports on the internet.
Has anybody seen something like this?
Could you have a look at my site www.justrunlah.com and check if something is wrong?
Can you even reproduce it?
Screenshot:
thanks a lot in advance
Try hiding the search bar within your website (header-search) and see if the problem still exists (just to test to see if its your own searchbar that's causing the problem).
It was some sneaky code added by a plug-in.
More specifically: Sweet Captcha used a code connected to Errnio to monetize
I removed the plug in and it's gone
Read more: https://wordpress.org/support/topic/hidden-search-bar-features?replies=3