Extjs Scroll Issue fixed in version 6.0.1 but i need to get that changes in
Version 5.0.1. Is anyone have any Idea how to apply changes? Thanks in Advance.
The bug fix applied to source code in Ext JS 6.0.1 may have a different implementation than 5.0.1. There are only two ways to backport the fix. The first is to identify how and where Sencha fixed the bug in 6.0.1 and then adapt the changes yourself to 5.0.1 using class overrides. Alternatively, you can ask Sencha to apply the fix to 5.0.1 either in the forums or by submitting a support ticket.
http://docs.sencha.com/extjs/6.2.0/classic/Ext.Class.html#cfg-override
Related
I currently have a NuxtJS (VueJS) project with Tailwind in it (latest versions).
I am using PhpStorm as editor.
For some reason I have no auto completion of suggestion for Tailwind CSS.
I have tried a lot of different things (anything I found on Google) but so far nothing helped.
Can anyone help me to find out what is wrong and how to fix this?
Latest thing I tried was a npm ci and Invalidate Caches/ Restart in PhpStorm but that did not help unfortunately.
I am using the latest version of PhpStorm.
Are you using "jit" mode? With it, code completion list is very limited, most of applicable CSS classes are not suggested. This will be fixed in the scope of WEB-50318, please follow it for updates.
Note also that, when using latest tailwindcss versions, the completion includes unrelated CSS classes from some *.test.css files. This will be fixed with the next tailwindcss package update, see https://github.com/tailwindlabs/tailwindcss/issues/4393. Workaround: delete node_modules/tailwindcss/jit/tests/ folder, it's not needed.
Ran into this problem with WebStorm and the previous answer diddnt solve my issue. However, I was able to solve it by instead of using mode: 'jit' in my tailwind config, by adding the --jit compiler option. Restart WebStorm afterwards.
I need a fresh download of FA version 4.0.3 as the CMS I use contained a damaged copy. I tried using the latest (4.7.0 at this time), but CSS changes in the .fa selector cause placement issues. I'd like to roll back to 4.0.3 to maintain compatibility until we can do a whole-site regression test for this type of bug once we upgrade.
Instead of complaining in the comments, I'll just drop this in here as a weak answer.
Either you download and stash it somewhere because you need to make changes (and then reference the CSS and other assets in the appropriate way as desribed on the Get Started page) or you use a reference to a CDN in a link to a stylesheet, in which case you can specify the version in the URL.
It sounds like you are doing the former, but you should be sure. Maybe you can just use the CDN link? At any rate, you can fetch 4.0.3 from the GitHub repo
I was able to get a hold of v4.0.3 via the GitHub Releases feature.
Having done that, I discovered that somebody had modified the CSS file in our CMS to add margin-right: 5px -- and it was one of the CMS's developers! Naughty, naughty!
SO, the 'incompatibility' I saw was not between the official, unmodified 4.0.3 and 4.7.0 versions of FA. Sorry about the false alarm! And thanks for your help. :)
Im using primefaces/ckeditor and experiencing some issues with performance on large amounts of text under IE11 (this doesnt happen under Firefox)
I am wanting to test the impact of removing some plugins/extensions - but cant find a list of whats installed by default.
I suspect the list is defined under -
https://github.com/primefaces-extensions/resources-ckeditor/tree/master/src/main/resources/META-INF/resources/primefaces-extensions/ckeditor/plugins
Can anyone confirm this?
I don’t understand why this was elected to close – but the answer can be found under build config -
https://github.com/primefaces-extensions/resources-ckeditor/blob/master/src/main/resources/META-INF/resources/primefaces-extensions/ckeditor/build-config.js
You can see the selected plugins if you follow the link listed under build-config -
http://ckeditor.com/builder/e6b8a045f8f984a69463975ca3e6524a
I am learning how to build simple extensions that use content scripts. To do so, I am tweaking existing sample extensions to get a lay of the land -- or at least that is the goal.
Problem is, none of the sample extensions that use content scripts seem to work for me. Two simple ones that should work but are not are: Email this Page, and SandwichBar (Direct link to zipped extension folder http://developer.chrome.com/extensions/examples/api/infobars/sandwichbar.zip ).
I am using Chrome 16.0.912.75 on a Linux box. Any ideas why this might be the case? Conflicting extensions or overriding flags? I would really appreciate any suggestions.
Thank You!
Sandwitch bar do not work because it uses info bar experimental API manifest version 2
Probably because you're using a really old version of Chrome (in internet years at least). They change the APIs from time to time, and probably something they've done in the interim has broken content scripts in Chrome 16 (for example the change from sendRequest to sendMessage). Isn't a more recent version of Chrome available for your platform?
I was working on a site some months ago and I used mootools menumatic from one of the resources sites from the internet.Firefox 4 was still beta at that time and I didnt tested my menu in it and currently i tested in firefox 4 and amazingly the script didnt work.where might be the problem.Thanks in advance.enter link description here
you use mootools 1.2.0 - just so we are clear on a few things here, and I am repeating myself but there you go...
mootools 1.2.0 is now 3 years old - http://ajaxian.com/archives/mootools-12-released - june 13th 2008. at the time of release, firefox 4 was not even a design concept.
mootools 1.2 relied on feature detection - read the previous thread linked above - and on the now deprecated getBoxObjectFor to determine if you were in a gecko-based browser like FireFox. Running this small test in FF4 on your site:
(via the firebug console):
JSON.encode(Browser.Engine);
"{"name":"unknown","version":"","unknown":true}"
Bottom line is, the menu works but it creates a javascript exception when trying to use specific style setters/getters that will fail due to the framework not understanding the browser version. This is likely NOT going to be the only error but you will need to write some extensive tests to catch all problems as many may result in different/undesired functionality rather than outright exceptions.
In short, the answer you may not want to hear: upgrade your mootools to AT LEAST 1.2.5.1 or ideally, 1.3.2 - you may need to use the compatibility mode version so your old plugins continue to work.
Other breaking changes: Function.bind used to take args of bindObj, [args] and is now natively defined as bindObj, arg1,... argn
And finally, you may want to accept some answers, 50% is way too low