FYI: Browser CSS Support:įirefox and other Mozilla browsers (IceWeasel, etc) use Gecko. The solution is preventing it from doing so by using -webkit-backface-visibility: hidden. Once the Chrome window’s display width gets to double the transform: matrix scaleY (last) value, the object flips backwards, making it invisible (see ). Many, many thanks, Dmitri! Nerd Stuff (Extra details provided by my husband. I did not use -webkit-transform: translateZ(0) because it caused issues with my Captivate VR projects. I was able to take his solution for a similar issue and, with my husband’s expert help, to modify it for the Captivate playbar. Special thanks to Dmitri Semenov, who posted: It also didn’t completely rid me of the problem. Resizing is a pain (always backup!), and the playbar became too small to use. After all, this set of problems didn’t start until I flipped the scalability switch! Other things I tried that didn’t really work at all: jpg files that do not look nice at full-screen anyways, making not scalable could be the best answer for you, for now. So, I do not recommend this… for my situation. I don’t have time to change my resolution, so why would I expect this to be an answer to my users? I worked so hard to make things scalable! What’s the point of switching to SVG images if I can’t scale up? It’s painful to watch a tiny version of my training on my 28″ monitor, only to have the same training be slightly too large for my laptop.
Sure, this works, but I lose the ability to resize my web-based training training this way.
ADOBE CAPTIVATE 9 DELAY ACTIONS BY NOT WORKING CODE
I found the div id for closed captions and added it to my code below, but it made me nervous that there may be some other object to which this could happen. This prevents both the playbar and the closed captions from disappearing, by adding a new css style for browsers that use the webkit calls (I added an FYI list of css support for many browsers at the bottom of this page). (Note: this is the same as the TLDR at the top of the post). Things I tried: Option: Add code to your index.html file or index_scorm.html I wound up being able to fix this in the tag of the index.html file. If you can shed more light on this, please let me know! I’m taking a risk that this stylesheet rule is benign enough not to wreak havoc on things. The reason that I don’t recommend this option to most people is because divs are everywhere and apply to everything. I wound up going with a different-but-similar solution in using a style on all div elements. Fixes:Īt the top of the page is my recommended fix for the majority of users. The first search on the list is the one that got me to where I needed to be. Since it was only Chrome and only, I realized that this wasn’t a Captivate search, but a search in the web dev world. After further inspection, we were able to trace it to a CSS issue. By opening the inspector panel, the available space shrunk to under 1358px, so it “magically” appeared again. We learned that the playbar would disappear at any width wider than 1357px. When the panel opened, suddenly the playbar reappeared! When we closed the panel, the WBT got bigger, and the playbar and CC reappeared. I enlisted my husband, who opened the inspection panel in Chrome (press F12 to toggle the inspector open/closed) to inspect the playbar element. I could hover over where the playbar should have been, and the tool tips would appear… there just weren’t any buttons to go with them! I didn’t notice at first, but my closed captions were also gone, too.
My overlayed playbar just disappeared! Vanished! Both in the LMS and locally, they were gone on my big screen. The monitor has a max res of 3840 x 2160, but it was only set to 1920 x 1080. And then… alas. Then, I tested it in a maximized Chrome browser on my 28″ monitor. My Captivate 2019 project – a newly scalable, 1280 x 720, HTML5, SCORM 1.2, 60MB beast – worked perfectly! Uploaded to the LMS flawlessly! Played in IE! Played in FireFox! Played in Chrome! SVGs worked! Life was good. Let me know if this helps! I like feedback 🙂
0 kommentar(er)
