https://www.dartlang.org/samples/
I have the latest version of Chrome Version 34.0.1847.131 m
None of the polymer samples work in the browser, I just get a blank box where the sample should display.
I tried on IE and Firefox, 4 of 6 samples work fine (none work on Chrome).
Defining a custom element - broken
Searchable List
Get input from a form
TodoMVC
Polymer and internationalization - broken
A task management tool
Is there something I need to do to get them working?
Background - I want to develop the equivalent of a desktop application that I can run in the browser as a learning experience and try to use a widget UI library.
There's nothing you should need to do for these to work. They all work for me in latest (stock) stable Chrome without any adjustments (36.0.1985.143 (Official Build 287914) m).
I would check the console for errors (press F12 to open the dev tools), and also try in Incognito Mode (which should disable most/all extensions) to see if there are any clues.
Related
I've recently began to work with Ranorex and already got Firefox and Chrome working. Internet Explorer only seems to track dom elements for me. I don't get the usual elements I get in other browsers thus I can't track or run any tests.
I've already tried to reinstall ranorex, restart the computer, trying to deactivate security-features in IE and setting a few different ranorex settings.
I've tried ranorex 6.1 and 6.2.0 and for Internet explorer I am using the most recent version. Windows 7 64 bit.
I would love to hear any suggestions which I could still try to get it to run.
Thank you,
Christopher
Have you tried to turn off the Protected mode and the enhanced protected mode?
I'm having a lot of trouble getting the JQuery Sortable functionality working on my Windows 8.1 device which is running ie11.
I had this working on an iPad through the TouchPunch library, but I've had no luck with the new Dell Tablet I'm working with.
I've ran the webapp through Chrome on the tablet, and the sortable functionality works very smoothly. Does anyone have any ideas how I can get it up and running on Internet Explorer 11?
I have tried pulling down various versions of Touch Punch on GitHub, some which attempt to deal with ie10, but I've found nothing that really works with ie11, so I would be glad for some pointers. If I run the [Jquery Sortable Demo][2] on the device, I am able to drag just about by holding to the left of the table row and pulling down at the right point, but this is in no way usable.
Ideally, jQuery mobile would include the sortable functions, but it does not.
***Just to be clear, if I go to the sortable example below on my tablet:
Jquery Sortable
then I can't really get the sort funcitonality to work.
To the above source code, I have added touchpunch library, and also added
-ms-touch-action: none;
to my #sortable class.
According to some online, this should fix the issue on ie10 and ie11, but I'm not seeing it make the remotest bit of difference.
Thanks!
Okay, there was a simple answer to this in the end, although it took me a long time to find it. I started by trying to intercept touch events and failing, which eventually led me to realise that I had added the site to Compatibility View (Settings -> Compatibility View Settings), where I also had checked "Display intranet sites in Compatibility View" and "Use Microsoft Compatibility lists").
I think this reverts to the site displaying in ie7 mode. Due to this, I think there are issues with the MS-touch commands being recognised, and so -ms-touch-action: none was having no effect.
To be clear, then, referencing touchpunch, whilst also using -ms-touch-action: none, should get the jQuery sortable functionality working in ie11 - just be sure to check your compatibility settings!
To be more secific, here is my dilemma.
I am planning to start UI test automation of an m.com site.
Option 1 that have been put forward is to use commercial tools (quite costly) that runs these test cases on the device. In addition to tool cost i also need to procure devices
Option 2 is to use open source tools like webdriver, change the user agent for browsers like firefox, chrome and safari and run the test cases on a PC. (This is quite cost effective).
I prefer option 2 but here are my doubts
1) Is the webkit rendering engine same for ios and mac?
2) Is the blink rendering engine same for PC Chrome and android Chrome?
3) Will changing the user agent, but using the same browser and running the test cases (eg: change user agent of safari in PC to that of ios, but render in safari) give me the same results as that of testing on the device?
Safari- browser in iOS and Mac uses Webkit as its layout/rendering engine
PC Chrome, Android Chrome uses Blink from April 2013 onwards
Having said that, iOS, Android browsers are compliant to standard HTML,JS, CSS syntax and standards, apart from that each browser may have their specific extensions or bleeding edge features, which may not be yet standardized.
Your testing is based on standard features, you need not worry much about the browser difference now.
Also, If you want to save headache of managing multiple browser, platform, you can try saucelabs.com (cloud based service selenium,test automation service)
I'm working on a software that includes 3D graphics. Those are massive enough, so I decided to use OpenGL to keep a quite fluent animation. I selected THREE.js graphic library (WebGL).
Reading the html through a Web browser works very well : WebGL functions are recognized. I did it on my desktop (Win32/Firefox17, please do not judge me on my configuration !) and on a Nexus 10 (Android 4.3, FF24 and FF25Beta, tried with Chrome30Beta but no joy...). But I need to access native data, like the file system, to get informations for my program. So I wrapped my code with WL, and deployed it as an app on my Nexus 10... And so disappeared the WebGL capability... :(
So I looked for a reason to that :
I found on the IBM site two different ideas : in one way, I understand that a JS engine is embedded, in another that WL uses the engine of the default Web browser of the tablet (what I understood the first time)...
Let's be precise with the different engines : On the Nexus, FFs have obviously Gecko engines, Chrome30 is a Blink (webkit-like, version 537.36). Those are the ones detected by window.navigator.useragent as I read directly in the browser, no surprise. In the Eclipse/WL preview, I got different interpreters, depending the browser I selected, FF or IE (not Safari, I don't have it installed), but not the one from my desktop (the ones used are even older than my own FF...). But, when I detect the one used in the app (after wrapping in an apk), it returns an AppleWebkit 534.30/Worklight/6.0...
Maybe I'm wrong (tell me), but if 'Worklight' is in the version of the engine, and if webkit is used even when I suppress Chrome from my tablet (the version is different, but who knows..), I wonder that, for this app, as it's configured, the engine is embedded by Cordova or WL.
If it is so, I agree it allows to read a code with a fully-compatible interpreter, regardless the browser installed on the hardware. But when a webkit engine does not please you for the functions it supports (like WebGL, very partially supported), it looks a problem for me.
Does anybody have a confirmation of how it works ? If the engine is wrapped with the app, do you know if we can choose the one to be included, or configure it (like enabling WebGL ;) ) ? Another idea ?
Thanks,
Vincent.
Worklight applications do not bundle an interpreter. The application will use what that is bundled in the OS.
In other words, the default WebView in Worklight is the one that the OS provides, in the case of Android it uses the bundled WebKit.
This is not something Worklight controls what-so-ever.
You could, maybe, somehow, bundle in your app the Firefox engine libraries and hook it all up together, but the task to do so is incredibly large and complex in size... and not supported by IBM Worklight. Also, I do not know whether Cordova supports this as well ( it is used in Worklight to interface with native functionality).
As for the useragent, the string "Worklight" is attached to it as part of support for IBM WebSphere Portal.
I have been working with Watin for about 1 week. I really wanted to make firefox work but had to give up after a day or so when seeing there was no way i could get jSSH working with Firefox 8 etc. Really wish there was a way of using Chrome or firefox i have to say
So returning reluctantly to IE I developed some automation software using Watin, however I have a persistent problem with Goto(href) where it seems as though the page never actually gets marked as complete. And although the browser navigates to the page and I can see the page fine, the call to Goto() just times out. After that point anything I try fails and it cant find the elements in the dom and I cant click anything programmatically. So I have to solve this timeout issue
I have read various articles suggesting fixes and have tried them all as far as I can see i.e. making sure I run as administrator, making sure that internet explorer enhanced security is switched off, etc.. I would really, really like to make Watin work - but right now I am about ready to give up and create a much, much simpler class with an embedded browser in my app. So stackoverflow is my last port of call. How can I stop Watin from timing out.
I am on Windows 7 Ultimate Version 6.1.7601 Service pack 1 build 7601
Visual Studio 2010
compiling as a .net 4.0 app
IE 9.0.8112.16421 with update KB2586448
I have a console app, no threads, [STAThread] on my Main entry point
This is my Visual Studio info:-
Microsoft Visual Studio 2010 Version 10.0.40219.1 SP1Rel
Microsoft .NET Framework Version 4.0.30319 SP1Rel
Microsoft Visual C# 2010 01021-532-2002102-70185
Any help will be very greatfully received.
Regards Julian
ok, so after many months of playing and fiddling the answer to my question has several parts.
Firstly. I needed to get Watin working properly as an embedded browser in a win32 application rather than as a console app. This required me to spend a huge amount of effort getting Watin embedded the way I wanted, I had problems with STATHREAD (of course), and the pop up dialog watcher, and getting the HWND of my browser into Watin to create its browser object (I used another sample on stack overflow to do this) and then I had to ensure ScriptErrorsSuppressed=true and I finally got it working. Hoorah
However, the problem I originally had all that time ago still seems to remain with Watin.2.1.0.1196 in dealing with frame sets on asda.com.
So I have just now done a svn checkout of the watin project and I am finally hoping that the latest updates I have seen will fix this problem once and for all... and Yes I am still really looking forward to Jeroen getting IE9 or indeed any other browser working with Watin. Working with IE (any flavour) sucks
WaTiN does not support IE9 fully yet as far as I know. Jeroen (the creator) is working on getting it fully compatible with IE9, but IE9 relies on new WPF components in regards to previous versions of IE, so i'm guessing this will take some work.
We suffered from several problems as well when we upgraded our WatiN tests to IE9. In the end we force our website to render everything to IE8 standards and set IE9 to IE8 rendering mode untill there is an update from watin to fully support IE9 with all its quirkcs and features.