I would really love to use Bootstrap 4 and its flexible grid system, but at the same time I need to support IE8 and IE9, so I am searching for ways how to make this work.
I have tried the flexibility.js, but for some reason, it's not working for me at all (see https://github.com/10up/flexibility/issues/51).
I was also thinking of using some condition that would generate a normal Bootstrap 4 grid without a flex option, but not sure what would be the best approach.
I would like to discuss about the best possibilities how to provide flex Bootstrap 4 for IE8 and 9.
Related
Just starting to use vuetify - really good stuff.
How can I wire up an HTML editor like quilljs.
I saw this post here; https://github.com/vuetifyjs/vuetify/issues/3550
Ideally.. I would like to use them both in codepen so I can get a designer to work on some bits and piece.
suggestions?
I created an editor for Vuetify based on Tiptap: https://github.com/iliyaZelenko/tiptap-vuetify
It is planned to make it as flexible as possible and develop many plugins for it.
You can support by giving a star to motivate me to develop.
I just have learned about vaadin and I'm watching tutorial about a CRUD TODO list in youtube. Vaadin uses Valo theme for css rendering that I found great but I'm wondering is it possible to use w3.css framework within vaadin vue code ?
I try googling but no answers.
It depends™
If you are asking: can is just replace Valo with W3.css the answer is most likely no, at least out of the box. The reason for this is, that Vaadin client side code emits the HTML-code you see in the browser and all style and class tags there are defined on their end. So what any theme for Vaadin must do, is to provide styling rules for that exact schema; so you would have to find a way to adapt. Or you have to put addStyleName all over your code (if it's btn in your CSS framework, it's v-button in Vaadin and also nested elements might be different etc).
Yet, if you just want to use the styles for some parts of your application (let's say, you want a fancy start page or add cards etc), then you can add the other CSS and use them together. Vaadin/Valo does a good job in isolating their styles from the rest of the page and also within their hierarchy (the theme name is a prefix to all Valo rules). Yet if the two themes then look great together is another story, but Valo itself allows for quite some tweaking just with variables put in SASS.
I have a joomla 1. 7 website and I have installed a widget kit for displaying a slider with buttons on it. It works fine in the backend, however it does not display on the site.
Is there a reason why widget kit is not compatible with Joomla 1. 7?
Without any details at all, I'd suggest a possible conflict with you chosen joomla template and javascript library(s) like jquery or mootools.
Try one of the simple templates that came with your joomla installation and see if the problem on the front end persists.
Widget Kit is compatible with Joomla 1.7, however as Grag P said, it might possibly be a conflict with another extension using Jquery.
Use Firebug and look at the scripts being loaded in the <head> tags and see if there are 2 Jquery libraries being loaded.
If so then the 2nd one is most likely coming from your template in which case go to your template manager and see if there is an option to turn off Jquery, else if its coming from another extension, try disabling it and seeing if this solves the problem.
Also make sure you have the most up-to-date version of widget kit as Yootheme have brought out a lot of updates in the last 2 months.
I'm using asp.net MVC3 to create a website,but the webpage can not adapt to different browsers and resolution though i use the % in my webpage,anybody can help me?
Not sure what is not displaying properly.
I use the css grids and fonts from the Yahoo User Interface APIs. This takes care of the basic browser differences for me. Then I just add my HTML and CSS. Go and download the framework, it is really good. It will help you get a solid base for your CSS from which you can build.
All the best.
My team is developing a website with a pretty complicated UI; jQuery, ASP.Net AJAX, etc. Of course I want my site to be compatible with all the modern browsers. Sometimes, in testing or general usage of the site while it is being developed, IE8 tells me that the page doesn't work in standards mode and it is switching to compatibility mode but it never tells me why. Is there some log or report or setting or something in IE8 that I can use to find out what upset IE8 Standards mode? Everything seems to work fine in FF, Chrome, Safari, and IE7 so what is it that IE8 doesn't like and how can I find that out?
The issue has to do with the styles that you are using which IE8 layout engine has trouble interpreting. Unfortunately there is no comprehensive list of style combinations what will trigger this behavior. You have the ability to turn off the automatic recovery on your own machine by going to 'Tools->Internet Options-> Advanced Tab -> Browsing -> and uncheck 'Automatically recovery from layout errors ..."
This is of course only applied to your machine and is of no benefit to your customers if the layout error is triggered. I do not have an answer to your specific issue, but I'd suggest validating your css against the W3C CSS validator:
http://jigsaw.w3.org/css-validator/
Any try removing complex styles one at a time until you find the combination that is triggering the error for your site.
Probably not an actual answer, but FWIW if it's complaining about the page as delivered (e.g., before you manipulate it with the DOM), you should be able to find out what it's complaining about if you pass that same page through the W3C validator. Of course, the validator checks against the validator's interpretation of the standards (which is very good though possibly not perfect) rather than Microsoft's interpretation of standards (no comment), so the two may not always align...
I suppose there are several issues that could cause IE8 to change into Compatibility Mode, but the style that I found in my site was using a pseudo element on the body tag. Removing this stopped IE8 from automatically switching to Compatibility Mode.
Removed this:
body:after {
// This causes IE8 to freak out and change into Compatibility Mode!
}
Check at Quirksmode to see if they know of obvious causes.