Just upgraded to Windows 10. Switching to SOURCE mode in CKEditor crashes the entire browser and cases to refresh. No way to access source.
Microsoft Edge is a new product, and so far, it has quite a few issues that need ironing out.
CKEditor introduced initial Edge support in version 4.5, but there are quite a few bugs that were reported by us to Microsoft and that need to be fixed on their side.
The issue that you describe was actually reported by us, too, you can find it here: https://connect.microsoft.com/IE/feedback/details/1577449/edge-browser-crashes-when-using-ckeditor-toggling-from-wysiwyg-to-source-mode
Anyone interested in having this fixed is probably most welcome to comment the bug report to highlight it's a show-stopper for many users. Sorry about any inconvenience caused.
As MicroSoft says this problem has been solved after update 1511.
Check this link: Browser crashes when using CKEditor (toggling from WYSIWYG to source mode)
Related
I have the latest update for Nightly (34.0a1 (2014-08-14)). It addressed one of the two problems I have from the previous update, which was the disappearing input fields. The other problem was the shrinking of the Google search field. What can I do to fix this?
See screenshot here.
#Acnologia, we are aware of the issue and have logged a bug with Google for them to fix the issue. You can follow along on here if you need more details.
The way I worked around the problem was to close Nightly, open Internet Explorer, and then re-download Firefox Nightly over the version I already have (DO NOT DEINSTALL!). Apparently it reset the version back to "34.0a1 (2014-07-21)" - before the "Google Search Results Page Searchbar Too Small" issue started. Then each time I start Nightly and Windows7 asks me if I want to allow the application to make changes to my computer, I answer "No" so Nightly does not get updated.
Then, each evening after I get home from work, I Google the past 24 hours to see if the issue has been fixed yet, and I will not update Nightly again until it has.
I realize this is a cheap workaround, and I would love to be able to trust Nightly Updates again, but this common issue should have been foreseen before the build was released. - And I will give them another week or two to figure it out, and if not... bye, bye Nightly!
I have had some long standing code which has worked fine for quite some time. Recently it began generating the following error. 1st on a asp site and later on a .Net MVC site. Neither of which have changed. I really curious as to why the this error now is rising. I am hoping this post will be of use to someone in the future since the solution was difficult to find searching the error itself.
Error:
ABCpdf error '80070000'
Unable to render HTML. Unable to get printer device-mode size. Microsoft XPS Document Writer Windows error 5. Access is denied.
Some research suggest that it is because the xps writer is not installed but this was not the case or that permissions were set up incorrectly.
http://www.websupergoo.com/support.htm# Support issue 6.7 number 4. Add the line below to the object and it worked.
Doc.SetInfo(0, "HostWebBrowser", "0");
This did the trick in both cases.
Just FYI, I think the ABCPdf 8.1 release addressed this issue.
Have you got the new version of ABCpdf 8?
As with older versions they use the IE rendering engine, if you upgrade the server/machine which is running ABCpdf to IE8 or higher abc pdf no longer have access to the rendering engine and will produce some very very odd results.
With 8 and above I have found the most consistence rendering is gained by changing the rendering engine used
theDoc.HtmlOptions.Engine = EngineType.Gecko;
this means youi are also not using IE which can only be a good thing.
We had this issue at work after some server updates. I resolved the problem by going to printers on the server and deleting the Microsoft XPS printer.
As soon as it was removed our PDF rendering came back!
Hope this helps!
I recently started using the Dojo firebug extension. I had gotten used to it since it had some nice features (letting you see dojo on the widget level). This was good for me because I am in the process of trying to learn dojo so this really let me see how stuff worked together.
My question is, has anyone found any solutions to get the Dojo firebug extension working in Firefox 6 or should I just try downgrading to FF5?
Thanks
UPDATE:
I tried a workaround I found somewhere else. It said to use the Firefox nightly build add-on, and that add-on would allow me to override the version compatibility. I tried that and it still didn't work.
I recommend trying the Add-on Compatibility Reporter extension from Mozilla. This extension (besides letting you report incompatible add-ons) lets you completely disable version checking.
It's a great way to ensure that older extensions still work when Firefox upgrades the browser every week. Now, this assumes that the issue is with version compatibility, and not that the plugin is actually broken! If it's the latter, there's not much else you can do.
(Also, that's an awesome plugin. I'm definitely going to try it out myself here shortly!)
Please take a look at this code:
http://3wcloud-com-provisioning-qa.appspot.com/testAjaxDojo
Just tab off the "domain" input field to try to make the Ajax run.
(Note: the test Ajax web service always sends back the same message, it pretends to check if domain is available but it really doesn't).
When running in Firefox 3.5, I get "dojo not defined" on the dojo.xhrGet statement.
It works fine in IE7 and Chrome browsers, and one friend tested on Firefox 3.0 and it worked.
1) Is there something wrong with Firefox 3.5 not properly getting the dojo javascript from the CDN? Possibly a caching issue?
2) Do you Dojo gurus know of this problem? Is it something that has already been reported to Firefox?
Thanks,
Neal Walters
Update: 9/1/ afternoon - I have uninstalled and re-installed Firefox 3.5.2 (but I kept my profile settings), and got same problem. I'm on Windows Vista Ultimate.
Finally found the problem. It was the add-on called "No-Script". Even though I had set No-Script to allow scripts globally, something in that tool was causing the issue. I upgraded to new version of No-Script and still had problem. If I disable the add-on (from the Tools/Add-ons screen), then Dojo loads perfectly from the CDN and life is good again.
I probably lost 6-8 hours on this stupid issue. Hope this posts saves someone else the time. Please "vote-up" the answer if it does.
As I stated in my comment, on Firefox 3.5 (mac) works fine. Try to do the following on your Firefox browser, insert the dojo library url in the url bar:
http://ajax.googleapis.com/ajax/libs/dojo/1.3.2/dojo/dojo.xd.js
Usually it helps to solve any cache problems and forces Firefox to fetch the file.
If it still doesn't work, just store dojo in your server and use it locally.
It's working fine here with NoScript enabled.
I just needed to allow both "3wcloud-com-provisioning-qa.appspot.com" and "ajax.googleapis.com".
Any ideas why after upgrade from IE7 to IE8 RC1 I may got:
'The ordinal 650 could not be located in the dynamic link library iertutil.dll.' error?
Check if IE8 was correctly installed. Go to Help, About IE and check version.
In my case, having downloaded IE8, the version which appeared installed was IE7.
Another point: The error message always appeared after Windows had downloaded the following update: Microsoft.NET Framework 3.5 and Microsoft.NET Framework 3.5 Family Update (KB951847).
If your system downloaded the above referenced update, try a System Restore. It's good for a short term solution.
Take note that Microsoft has a toll-free and Free of charge help line for IE8 and only IE8. You may want to give them a try. Toll-free number: 1-866-876-4926 (US and Canada only)
Good Luck,
Vinicio
Absolutely unbearable how they release IE8 , my solution in this case was just downgrade to IE7 not the solution really but worked.
guys it means the IE8 regestry is missing look online for it