As I am converting my flash based virtual lab to HTML5 using EaseLJS, I thought its a good idea to ask if some one knows any browser support issues or restrictions? lots of new and old browsers out there ..
I wonder how easeljs handle such diversity, is there a known-compatibility-issues of easeljs APIs ?
A matrix would be perfect! well ?
Canvas is a pretty well-supported and consistent HTML5 feature - and there are very few inconsistencies between the major browsers. There are some touch issues on some of the mobile platforms that we are working to address - mainly Android.
Cheers.
Related
Most references as below mention that Safari partially supports web components.
In detail, what web component features are not supported by Safari desktop and Safari iOS?
Is there a technical docs or specs about the issue?
https://developer.mozilla.org/en-US/docs/Web/Web_Components
https://caniuse.com/shadowdomv1
Burn all old blogs!
Apple Safari supports Web Components, apart from Customized Built-In Elements.
After an ongoing debate since 2013, nearly everyone agrees Apple engineers are right on this one.
Not yet supported by Apple (Google proposals, implemented in Chromium):
Constructable StyleSheets : https://web.dev/constructable-stylesheets/
declarative shadowDOM : https://web.dev/declarative-shadow-dom/
Will never be implemented by Apple:
Customized Built-In Elements
extend from any existing HTML Element: <p>, <input>, etc..
If you want to understand the Apple Why,
read back in time to 2013 - Yes! Web Components are not a new fad!
Autonomous Elements (extend from HTMLElement)
work 100% in all Modern Browsers
At this time of writing, see: https://custom-elements-everywhere.com/
Angular is 100% compatible
Svelte is 100% compatible
Solid.js is 100% compatible
Vue is 91% compatible (Vue doesn't listen to Capitalized Eventnames)
React is 29% incompatible
StackOverflow Deep dive into Web Components, React & Lit like BaseClasses:
Main differences between lit-element & React
Javascript regexp variable length lookbehind is not supported by Safari but works in Chrome, Edge and Firefox. Maybe international agreements/standards say Safari doesn't need to support it (yet) but it's a pain nonetheless.
The forum post (see below) on the Apple Developer website has both requests to support customized built-in elements and formAssociated custom elements.
https://developer.apple.com/forums/thread/682165
It could be used to follow up onto when Apple will release support for those features on Safari.
Is there any way we could live stream "video/mp2t" content in the browser? I'm building a live stream app where some urls don't have any mimetype specified but the content is "video/mp2t". I've tried to use the major html 5 players: jwplayer, shaka-player, video.js, and none of them seem to support this kind of content out of the box. I've read that might be possible to transmux on the fly to mp4, do you guys know any example or some guidelines?
Android and ios seem to support this but the browser not, why is that? Do you think it's something to be incorporated in the future?
Thanks!
I've read that might be possible to transmux on the fly to mp4
Yes, you can write the code yourself, or base it on a another library like mux.js. But as you said, nothing does this out of the box.
Android and ios seem to support this but the browser not, why is that?
There are dozens or hundreds of container formats. Supporting them all would be ridiculous. Different companies, and different standard bodies make different decisions on what they think their users will require.
Do you think it's something to be incorporated in the future?
No, I don't.
I've been thinking to give GUI development a try lately and am torn with the choice of between wxPython and Mono.
Judging from what I've seen out there, wxPython people seem to use the WebKit trick to produce nice (doesn't have to be beautiful) UI.
How hard is it to do the following in each of the platform:
1) Custom Control
2) Use HTML rendering
I don't quite understand how far the HTML rendering works via WebKit in wxPython (i.e.: does it support separate CSS/JS files? how's the JS support? do we need to write extra wxPython code to run the JS? how hard it is to integrate between JS events and wxPython widgets? what are the usual strategy of integrating WebKit with wxPython?)
Mind to share your thought on this subject? I specifically pick either wxPython or Mono, not Java Swing for no reason.
PS: I'm aware of certain limitation of cross-platform UI (as in: it won't be 100% native) and I could care less of such things.
wxPython has wxWebkit available via the new WebView widget, but WebKit is only available on Mac and Linux right now. WebView uses a different rendering engine on Windows called Trident from IE (see http://wxpython.org/CHANGES.html). So you'll want to keep that in mind.
Either way, we're talking about browser engines that display HTML, CSS, etc. They should, theoretically, display whatever those engines support. You'll have to look up their specifications to be sure and also make sure to check if the port supports everything. As I understand it, they should definitely support the usual HTML and CSS and I would assume normal javascript. If I were you, I'd just create a simple window in wxPython and then load the web page you've created and see how it works.
I don't know how the javascript communicates with wxPython or if it even does. You'll want to ask on their mailing list for that kind of information.
I'm building a small app with Adobe AIR using HTML and JavaScript. When I view the app as a regular website (no matter in which browser), it's all perfectly fine. But when I view it as an AIR app (with the adl command or in a proper package), all the effects, mostly jQuery, make the website lag.
I do not use any fancy effects, it's just about image sliders. Any ideas where this is coming from?
Thanks!
PS: I know it's not because my PC is too slow; I recently bought new hardware for 700 EUR (~980 $; ~620 GBP) :)
I had the same problem.
It turned out, you MUST NOT use box-shadow -webkit-box-shadow or text-shadow css properties in your air app. It works fine in other browsers? but dramatically slowes down air performance.
That worked for me.
I'm working on a JavaScript AIR app at the moment that is running jQuery without a problem on very low spec PC, and is actually impressing me with how fast it is (knock on wood!). Adobe improved JavaScript performance recently, so if you haven't got the latest runtime (currently 2.7) then definitely grab that.
As for the jQuery itself, make sure you are using the minified versions of the jQuery libraries, and only include the ones that you absolutely need. It's always a good idea to compress images as much as you can, as moving big images around will obviously take more processing power.
You could also take a look at this article about performance tuning AIR apps, although it is focussed on Flex and AS development.
http://www.adobe.com/devnet/air/articles/air_performance.html
Good luck!
How to create a WAP website?
What software do I use?
Do I just need to use HTML coding or other type of language?
And after I created it, Can I view it on my own phone?
Do I need a server to let it run or I can just view it on my phone?
Can someone help please, its for my project.
Thanks alot.
What phones are you targeting? Any phone released in the last 3-5 years is able to view standard (X)HTML without issue - except for the fact that they mostly have very small screens.
Some phones do not support Javascript very well (but that is mostly changing, too) and most phones do not support Flash (yet - most newish phones except iPhone will probably support flash "soon", if not already).
The only other main difference is that most phones these days use a touch interface, rather than a traditional keyboard/mouse. That means you can't really do things like hover effects and so on.
But other than the smaller size, everything else is pretty minor.
I agree with the post above that unless you are targeting very old phones, there is probably very little point to working with WAP today - AFAIK the last official version was WAP 2.0 which was circa 2002.
WAP 2.0 used a streamlined version of XHTML. The best way to develop is to either navigate your phone to a standard HTTP server hosting your files - or download and use a simulator. I found the best practice was to develop the app until it worked on the simulator (which could often be directed to load local files) and then do final testing and tweaking with actual devices.