It would appear that bwu_datagrid is broken in the recent polymer release as none of my grids are rendered after upgrading. Could you confirm if this is so?
I just tried all examples (Dartium, Chrome) and can't reproduce your problem (Polymer 0.15.3+2).
Maybe you run into an issue like this https://groups.google.com/a/dartlang.org/forum/#!topic/reviews/KW8P4ZOcfIA which refers https://github.com/webcomponents/webcomponentsjs/pull/57 (I couldn't finde more information about the actual problem they are facing there but seems to be CSS and Polmyer > 0.15.2)
Related
We have an issue with Preview in Wagtail CMS. I have looked around at several other people that have had this issue but none are the same as mine. As preview is not even working in Dev and we are receiving no errors to suggest what the issue might be.
We Use Wagtail 1.13.1 & DJANGO 1.11.8
When i click the preview button It just takes me to a new tab thats blank with no error or anything.
if i inspect the button I can see:
<button class="button action-preview icon icon-view" data-action="/admin/pages/30/edit/preview/" data-auto-update="false">Preview</button>
So I took: /admin/pages/30/edit/preview/ and manually pasted into the browser and it gives me:
https://domain.dev:8000/admin/pages/30/edit/preview/
I am still receiving no errors, which leaves me to believe either a setting is incorrect or this is a bug in Wagtail as it does not work in Dev,Staging or Prod
If anyone can shed more light on this topic it would be greatly appreciated as at least if i got an error I could look to resolve it. but i get nothing.
Where am i going wrong?
This is an issue I've been experiencing only for the last few days; when following a link to jsfiddle, or even going to the jsfiddle homepage (on IOS 6, iPad 2), jsfiddle doesn't initialise properly, and all I see is "initialising the awesome". Even logging in and creating a fiddle doesn't work. The issue only seems to have appeared since some recent downtime which I assume they were updating jsfiddle during it. Has anyone else experienced this issue/have a fix?
NB: this occurs on both safari and chrome.
Alright, I've sent an email to jsfiddle support, and I came up with this response:
We're working on that.
https://github.com/jsfiddle/jsfiddle-issues/issues/330
For the moment please use draft feature or add /embedded/result to the
URL.
http://doc.jsfiddle.net/basic/introduction.html#draft-page
Regards, Piotr
Hopefully this means that the issue will be fixed soon, however, in the meantime, use: (for example)
http://jsfiddle.net/ (your fiddle)/embedded/result
I.e, just add /embedded/result to the end of the url as Piotr suggested.
I'm getting a weird error while trying to click on a Capybara Element
I'm using find(:xpath,"//a[contains(text(),'Connect')]").click
(find(:xpath,"//a[contains(text(),'Connect')]").present? return true)
the error I get is:
Selenium::WebDriver::Error::MoveTargetOutOfBoundsError Exception: Element cannot be scrolled into view:javascript:void(0);
i did some research and the only solution i found is that setting the selenium version to 2.16 may fix this issue (i'm using 2.25).
anybody got an idea?
It may happen when the page being tested is not fit into the current window size. If you know such pages where usually these error happening, you may explicitly scroll down before doing the operation on such hidden elements(like click, clear etc). Here the code to explicitly scroll down the page.
In java,
JavascriptExecutor js = (JavascriptExecutor) driver;
js.executeScript("javascript:window.scrollBy(250,350)");
From the times I used selenium webdriver to test .NET apps, I would get that error when the issue was exactly what it sounds like: It's looking for an object on the page that it cant scroll to for some reason. In my case it was because some dialogue boxes would appear without scrollbars and the driver had no way to "scroll the object into view"
Can you watch the execution of your test and see if that's the case? I had some luck rolling back to a previous version of firefox because 15+ was (as of about 2 months ago when I had the issue) unsupported by web driver and had this problem periodically. Rolling back selenium versions may help too.
First step though is definitely to watch the execution of the test and see whats happening though. And a good debugging idea may be to try to work through your steps manually yourself to make sure the test works by hand.
Its also worth noting that for the webdriver to be able to execute click the object actually has to be visible. IsPresent doesnt require that, it just searches the page files. Also an issue I ran into. IsPresent will still return true for objects that are not and cannot be made visible on the page (i.e. something at the bottom of the page that you cant see at the time)
Couple of tips here:
Webdriver should ideally be on the most recent update, it's what most use (Unless you're doing Ruby Automation)
Use css selectors, xpath (Whilst rendered), is almost always heavier on both resources and code.
Try defensive coding, first of all ascertain it exists. There are many ways to do that dependent on what package you are using. In ruby you would do page.has_css?('css_string')
A website of mine is behaving weirdly. The layout sometimes is fine, and sometimes it is screwy. An example page that I see the problem on is this one: link
Disclaimer: I have yet to start my investigation into cause in earnest. I am turning to Stackoverflow because I am lazy and I hope someone will say "That happened to me once, it is probably this...". So please, no one get stuck into this working out this issue if it is something you have never seen before, as it wouldn't be fair as I have not done it myself.
Ok, some background:
The problem usually (maybe always) occurs when first viewing the page
The problem does not show up always, only sometimes
When the page shows up munged, if you refresh it usually reloads looking as it should
The site is a rails app
The css is passed through the neat Smurf Gem, which automatically minifies the CSS and Javascript on the page.
The layout problems happen in firefox (both linux and winXP)
The CSS is served up in the production environment using the ":cache => true" option which concatenates all the css files into one file
Anyway, I am hoping that this has happened to someone before and it will be really simple to fix. If not, I'll go and investigate and return with the solution (or a request for more help).
Thanks in advance!
James.
[edit]I added the first two bullet points, inspired by the comments and first answer[/edit]
We have had something similar when using HAML and SASS that resulted in the CSS being completely unavailable. It only happened on deploys. We determined it was a combination of the Rails stylesheet merging and the generation of the CSS from SASS. Sass was not done generating the CSS, which it did so on the first request to the application, when Rails attempted to merge it all together. The result, a corrupt useless CSS file. Then we stumbled upon this article which has a solution for preventing this issue.
Based on all this, my best guess is that the Smurf gem is attempting to generate your file on the first request, but Rails is serving it out before its done. The generation completes then each following request is fine. If this is the problem then the only solution i know of is to get the file generated before the first request. Of course, this does assume that it is related to deployments or application restarts in some way.
Peer
I had such a problem. The problem was only at the first time the page was loaded. Just reload it and it was fine.
The problem in my case was that the images where not there in the cache for the first time so the browser didnt know it's dimensions when preparing the page which caused the problem
If an image doesn't have a height/width assigned to it, a place is created on the page and it's put there. If the image doesn't quite fit, the browser may not know this until it's refreshed. Then it already knows the size and can properly fit it onto the page.
I can't get IE to print my canvas (generated using excanvas)... I'm using the most recent version of excanvas.
http://dl.dropbox.com/u/997831/canvas.html
(Note: I already tried having the canvas element already on the page instead of creating it with document.createElement)
Unfortunately, there is no good answer here. There has been a ticket open for well over a year regarding the printing of excanvas that has yet to be answered. You could try the silverlight version of excanvas it's a little better but still suffers from similar problems.
The only way to get it printed properly now would be doing a print screen and then printing the image. Unless an newer version of excanvas comes out or IE9 is released, native printing on IE just isn't going to work.
my best shot currently is printing pre-rendered image
(see wkhtmltoimage on google code)