Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
This is my first question. I've searched all over StackOverflow and Google for answers but have been unable to find one.
I have a video embedded on my website using Vimeo's universal iFrame code. The video can be seen below and will play just fine with any Desktop Browser and iOS 5 device.
The problem comes with the latest update to iOS...
Now on iOS 6, the video will not play. Instead it'll be stuck in a "loading" holding pattern. Using iOS 6 on iPhone Simulator for XCODE yields the same result. The link to the exact video in question is below. Loading on an older iOS 5 device and the video starts playing just fine.
Note: the video does NOT play on iOS 6 Chrome as well, however works in iOS 5 Chrome.
http://www.seriouslyfunny.tv/2011/03/padded-room-promo/
Any ideas? I feel this is a stupid newbie questions and someone's 8 year old nephew will know the answer.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 4 years ago.
Improve this question
Do any of the commonly used screen readers emit browser events that can be scripted with javascript?
Or, are there current or planned javascript APIs to communicate with screen readers in the same way there are now APIs for working with other OS level systems (cameras, GPS, etc.)?
A similar question from three years ago (Evaluating current state of a screen reader in JavaScript) produced a definitive "NO" answer. Has anything changed since then?
I believe, it's still a No, but the closest to your request is the (drafted) Accessibility Object Model. It does not allow to interact with screen readers directly (it seems), but it does allow to manipulate the accessibility tree in a browser.
Currently supported at least in Chrome Canary via a command-line flag.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 5 years ago.
Improve this question
I have noticed that when I launch the Xcode 8 iPhone simulator that actions that I make when using the simulator run incredibly slow, for example, when I maneuver to the home screen by clicking Hardware>Home or Shift+cmd+H it runs fine but when I open an application the borders make a strange animation, and when I tap a button on an application, the transitions take a long time. Sorry or such long question, but any help will be greatly appreciated
Try This.. Unselect the slow animations in simulator debug
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 8 years ago.
Improve this question
I used to use Flash (Adobe Captivate) for creating CBT testing and tracking to a DB, but iPad tablet doesn't support flash, so I need to find a different technology. I also need to support older browsers like IE8 and am concerned about HTML5.
You can use Captivate 8. Best mode for what it sounds like you want is the Responsive Projects (which is not a powerpoint conversion). It publishes in html 5 and runs on iPads and other mobile devices. Seems to be several problems with Android devices, but translation to iPads for simple stuff is pretty sleek. SWF output is still an option with Cap 8, but it won't run on tablets.
Warning - it is new technology and seems to have some bugs, especially with video on the iPad. Firefox on the iPad has problems, maybe Chrome too. Personally I miss the design once, deploy everywhere days that we had with Flash.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 9 years ago.
Improve this question
I'm currently working on a project and we've noticed on a number of machines that when leaving the page open for a few minutes, Chrome (on OSX, haven't tried on other OS flavours) will eventually drop the google fonts we've chosen;
and revert to what appears to be Times.
This has been much more prevalent in the last day or two since the release of Chrome v32, and has happened on other sites with no relation to the site we're building.
Hovering over any instances of affected text will make Chrome update the font to its correct typeface again, and it will typically correct all instances at that time.
I'm wondering if anyone else has come across this problem before, and if there is a known work around to stop this from happening?
This is a confirmed bug (#236298) with Google Chrome, rather than it being an issue with your code.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
in my apps use storyboards ios5 content. If realized my apps for ios5, I would like to know how many potential users who do not have ios5 I lose? thanks
As of November 9 you would lose about 60% of the customer base, but that's only a few weeks after release. As time goes on that percentage will shrink a lot.
http://news.cnet.com/8301-13579_3-57321295-37/ios-5-on-almost-40-percent-of-iphones/
If the feature makes development that much easier, then go ahead and use ios5. If it's a minor convenience, then stick with ios4 (but make sure it also works well on ios5!).