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.
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?
Is it just me, or is the angular-material "Getting Started" example broken?
On that page (link above), there's an inline codepen to show using angular-material. But the demo doesn't work! (In particular, I don't see a button to collapse the sidebar.)
Since I used this example in my started project, I spent quite some time troubleshooting it -- to no avail. Then, I realized the example itself it may be broken. And sure 'nuff, it is!
Does anyone know what the actual bug is, so I can work around it on my test app? It must have worked at some time; but I can't figure out why it's broken now.
Thanks!
That particular pen is working fine for me but I have noticed a few are not working, and it's due to the angular-material.js link being incorrect in the dependencies (under the pen's settings) the link provided redirects to the CSS.
This is intentional - the sidebar only becomes collapsable on smaller screens and is open on larger screens. Shrinking your browser window will show the collapse button.
That being said, the Getting Started page is definitely in need of an update. It is a good guide for a basic page structure, but the individual demo pages will be a lot better if you're looking to try out some of the components. (Every demo has a CodePen link to open an editable version.)
I was using Twitter's User/Search API with no problem:
https://api.twitter.com/1.1/users/search.json
and
?q=myusername&count=20&page=3
But from yesterday, the paging property seemed not to work.
when I change page value, it returns the same page 1 results.
I even tested my query with https://dev.twitter.com/oauth/tools/signature-generator/ but nothing changed.
I'm sure that I'm not doing anything wrong because it was working yesterday. So what happened?
Thanks for your help.
Edit:
Well it seems something's wrong with twitter REST API:
https://twittercommunity.com/t/rest-api-people-search-json-not-returning-verified-accounts/31381
https://twittercommunity.com/t/users-search-doesnt-show-up-some-verified-account/31388
This issue is solved now. It was a twitter bug (PREL-11824).
More info: https://twittercommunity.com/t/users-search-doesnt-show-up-some-verified-account/31388
Looks like this problem has come back.
https://twittercommunity.com/t/search-problems-have-returned/32573/3
I've been using pixel perfect for quite a long time, and grown to love it (despite it's annoyances). Now, when pp is no longer compatibile with fx 6, I'm looking for a tool to replace it.
I found x-precise and am one step from buying it, but I don't quite like the necessity to include something in source page.
I know that I can do it myself, maybe not as good as xprecise or pp, but I just don't have time right now.
I'm curious to know what do you use? Or do you stick to old fx, just to use pixel-prefect?
I have been working for 3 years as a developer and created my own script for pixel perfect mode. http://jek-fdrv.16mb.com/pixp/
In Chrome, try PerfectPixel
https://chrome.google.com/webstore/detail/dkaagdgjmgdmbnecmcefdhjekcoceebi
I haven't managed to add a layer in PixelPerfect under any of last Firefox ..27.x.x builds - checkbox is locked. I tried PP versions older than 1.8 it didn't help. I tried to find a decent alternative and failed. Eventually I simply wrote a bookmarklet that provides a similar service http://dsheiko.github.io/pixel-perfect-bookmarklet/.
Pixel Perfect 2 for Firefox native developer tools is available:
https://github.com/firebug/pixel-perfect/wiki
Honza
Using the "Compatibility Reporter" seems to work for me so far. The only issue I recognized is a needed reload of the page, to see recently added overlays in the pixel-perfect list.
Just change line 15 in install.rfd file to
<em:maxVersion>10.0.*</em:maxVersion>
Also there are little issue with left position. To fix it change file panelAction.js at line 108 to
this.setPrefValue("pixelPerfect.lastXPos", this.findPixelPerfectXPos(overlayDivId) + 1);
at line 355 to
xPos += 1;this.updatePanelDisplayOfXAndY(xPos, yPos);
After adding new overlay just refresh page or reopen firebug
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)