Did anybody manage to figure out how to switch to an iframe in the latest Nightwatch 2.2.2?
For example, browser.frame(1) => seems deprecated.
The ELEMENT doesn't exist anymore in version 2.x.
This has been fixed with Nightwatch v2.3
Related
I'm trying to use IntersectionObserver in cordova 8.0.0 app which is running on ios 13. When I inspect my app via safari, I see an error on intialization:
ReferenceError: Can't find variable: IntersectionObserver
This would suggest, that IntersectionObserver is not available, and I should use a polyfill. But! I've read many post claiming that IntersectionObserver is nativly supported in iOS safari 12+. And I kinda assume, that cordova would be running nativly available WKWebView, so it should work without polyfill, right?
I've found that I've got IntersectionObserver enabled in my safari experimental features, so maybe there is an option/flag I could use to force enable this feature in my app as well? I'd really like to avoid using polyfill if it's possible..
Thx to any suggestions
We ran into this issue and there is one important thing to call out. While this has been fixed in newer Safari Browsers, this issue still can occur on older devices (despite fully updated Safari). This is due to the fact that the IntersectionObserver feature seems to be deactivated as 'Experimental feature' on older iPhones (I know for fact that this is the case for iPhone 8) - possibly to save resources - see https://youtu.be/qDSXYGybNVU?t=68. So to ensure your application to work you might need to use polyfill as an alternative/fallback nevertheless.
IntersectionObserver API is supported on iOS safari since 12.2. Yet it was supported via 'experimental feature' and enabled by default. I assume that experimental features are not enabled under cordova by default, so far I haven't found a way to configure it to be enabled.
An option is to use polyfill: https://www.npmjs.com/package/intersection-observer. I tested myself and performance is not good enough, it uses either setTimeout or MutationObserver to observe whole document with all options enabled.
I just added this checking
if ('IntersectionObserver' in window) {
// IntersectionObserver initialization code
} else {
// make lazy loading elements to be loaded right away
}
Enjoy
let me know if anyone else, also having the same issue. it is working fine with older version but I just installed the latest version and now it's not working.
I have faced the same problem today in morning when I have updated WordPress to latest version 5.
But I have fixed the Problem by updating the Visual-composer back end-editor to latest version.
Check this link. You can see Release Notes there that says VER 5.6 - Update: Compatibility with WordPress 5.0.
So just update your plugin & sure that will fix your problem.
Try it & let me know if you have any issues.
Use the plugin call classic editor. It uses the old editor. Do not use classic editor addon. Just the standard classic editor plugin.
You can use Wordpress Version 4.9.9
It is working for me.
Download link
I can’t find Backend Editor, where is it?
The WordPress admin panel is a very unpredictable environment for such a complex product like Visual Composer. Because of that, we decided to remove Backend Editor in 2.0 version and focus our development on Frontend Editor. As a result, you as a user are getting a more stable and faster editor. Release cycles will become shorter and new features will be delivered to you faster.
To justify the “loss” we will introduce new “structured view” mode in Frontend Editor (similar how it was in the Backend Editor) and there is always Tree View mode available (a layer style representer and editor of your layout).
official website
I use SonataMediaBundle with SonataAdminBundle with a simple install.
When i want to add a new media. I can select what provider i want. I configured it to show Daylimotion, Youtube and Image.
The Youtube and Image picture doesn't appears. I can see the error
GET http://my_url/web/data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAOcA…/kI5CVlcXzqGKBtUyZMjz8qd9WApPTb0NUnhAgBPwh8D8I22yw4XkRvwAAAABJRU5ErkJggg== 414 (Request-URI Too Long)
Second problem come when i upload an image. I got:
request failed: URI too long (longer than 8190)
I try the js i found at http://sonata-project.org/bundles/admin/master/doc/reference/troubleshooting.html but it doesn't work.
Edit: I change my SonataMediaBundle version from 2.3 to dev-master. Now i can see the youtube logo but still have the too long uri error.
I faced the same issue. I was using the sonata core 2.3.1 and changed to 2.3.0, This solved it. It seems that the 2.3.3 also having the same issue.
So make sure you downgrade your sonata core in composer.json until they fixed the issue. It is better to downgrade to a stable version than using the dev branch.
"sonata-project/core-bundle": "2.3.0"
By the way, i'm using the 2.3.1 for MediaBundle.
issue
Problem solved with an update to dev-master and a cache:warmup !
Please use only stable version otherwise you might have some WIP issues...
How to fix handlebar issue with nodeJS
TypeError: templateSpec.call is not a function
I had the same problem when I was pre-compiling my templates with a specific version and using them with a different version of runtime.
In my case, gulp-handlebars was using the edge version, and I had to install the version I needed and passed it to the gulp-handlebars configuration.
If your following a tutorial that uses an old version of the handlebars runtime. Replace handlebars.runtime.js with the latest version from the handlebars website.
I installed handlebars via npm and as soon as I used updated code, it worked perfectly.
I have been going through all the posts related to GCC with JQuery but unable to find the solution.
Is JQuery still not compatible to work with GCC? If not can you please refer to the appropriate link or provide an example?
The main distribution of jQuery is not compatible with Closure-compiler ADVANCED_OPTIMIZATIONS. To use the main build of jQuery you must reference the appropriate jQuery extern file in the Closure-compiler contrib folder.
I have an experimental jQuery 1.9.1 build which IS compatible with ADAVANCED_OPTIMIZATIONS. It is available on my GitHub account.
A version of the jQuery 2.0.x branch that is compatible is under development, but not yet complete.
Try adding this flag:
--process_jquery_primitives
https://code.google.com/p/closure-compiler/wiki/jQueryExpansions