Forum Replies Created
-
AuthorPosts
-
Steven Zahm
Keymaster@ martcol
The CSS scoped is newer and poorly or not properly supported by browsers, technically. They do not limit the scope like they should according to the new spec. Now, browsers have supported this use of CSS nearly forever. The purpose of the placement where it’s at is to provide the widest compatibility with these as possible with themes. A large chuck of that CSS has been added over time to deal with mostly themes that have made some poor CSS decisions that not only negatively affect Connections but any other plug that output in the front end too.
As I continue to drop support for legacy browsers, older methods will be phased out.
I hope these replies have been helpful.
Keymaster@ martcol
Yes, I am aware of validation errors. These vary depending on which doctype you run it thru. The majority fall into it complaining about legacy table attributes, use of short tags which are just self closing tags and are valid HTML5, the use of the data node which is valid HTML5, and a bunch generated by Google for their maps. The biggest no, no is that <p> tag which I should fix.
Really, the important thing is that everything displays properly across the various browsers. I use to spends hours on end making sure this was perfect to a tee only to have layouts break when used within the many thousands of themes in use. Most of the CSS and tables attributes were added only to ensure proper display in as many themes as possible while providing the broadest support for browsers as possible.
Keymaster@ martcol
Not presently without resorting to editing the core plugin files. I do get this request/question from time to time. I’m not certain if I get enough to implement this yet. I’d let to keep the settings options to a minimum.
Keymaster@ martcol
Off the top of my head, only two templates use tables at all and they should be cMap and Market. This is due to the persistence of legacy browsers and having to support tens of thousands of users using thousands of different themes and plugins all coded with varying levels of skill, self included. The use of tables in these two templates is primarily to support the columnar presentation within each entry. Certain legacy browsers had severe issues with dealing with floats properly. So, only the most basic structure is formed by the table the rest of the elements do not use tables at all and are very easily styled and easily overridden. Personally, I do not like using tables in this manner, but with these two templates it was near necessity/support.
Now, with that said … I’ve been slowly removing support for legacy browsers following the footsteps of Google, Facebook and WordPress. Version 3 of both those templates will have tables removed and legacy browser support completely removed [ie. some of the validation issue you expressed concern over in another forum thread].
KeymasterKeymasterYou can make the necessary edits to the class.form.php file. Just keep in mind you’ll have to make these changes again if you upgrade Connections to newer versions as they’re released.
KeymasterSorry, but I do not have an answer for this as I haven’t focused on creating a print solution yet.
02/08/2013 at 4:41 pm in reply to: Is there anyway to click on the business card and go to more details like BIO #251078KeymasterSorry, not presently. Look for that to come later this year. You’ll have to upgrade the template, but that’ll be a free update.
KeymasterThe Pro Add-on Pack question can be asked in this forum. I check you account, you should be able to access the CSV Import support forum now.
KeymasterPro Pack questions can be asked in this forum. Let me know if you can not ask it thanks!
-
AuthorPosts