Auto complete with linked CSS files

kybos · Post by **kybos** » Fri Jun 01, 2007 10:45 pm

Hi,

in the new version of the tools there is the possibility to get auto complete for linked CSS files in HTML documents.
I have two linked CSS files in the header but only the objects from the first one appear in the auto complete window.
Is this meant to work this way or an error?

Thanks, Kybos

Post by **Karlis** » Sun Jun 03, 2007 5:49 pm

I have no idea if I do not have the files.

Post by **syrupcore** » Mon Jun 04, 2007 8:06 pm

This is verified locally. I'm still using 2006 but with the demo I downloaded to help people here troubleshoot I have the same problem as the original poster. (8.0.0.71)

Create a new html doc with two linked external CSS files. Only IDs from the first css file show up. If the the first is a link to an empty or non-existing file, nothing comes up in the ID auto-complete box.

Will

Post by **syrupcore** » Mon Jun 04, 2007 8:57 pm

I'm also seeing something else a little weird. I use a lot of descendant selectors (like .faq h3) in my css so that I don't need to class and ID everything in my html. when I type class="" in the html, webuilder offers me those selectors as well but they're not really classes that you would attach to anything in the html.

I hope that makes sense.

thanks,
Will

Post by **Karlis** » Wed Jun 06, 2007 1:54 pm

The second is not very important but I will look into the first one.

Post by **syrupcore** » Wed Jun 06, 2007 10:48 pm

no, not important at all. just a little odd and in the way since they can't be used. I'm not sure how most people write css. I think most people write a class/id for each thing. I tend to use descendant selectors because I favor clean html and dirty css.

ignoring anything with a second word in the declaration might do it.

.faq {} = use.
.faq .foo {} = ignore
.faq h2 {} = ignore

kybos · Post by **kybos** » Thu Jun 07, 2007 11:26 am

Hi Will,

I think this is a matter of taste.
I personally would like to see all available selectors in the input help, even if it's clear that some can't be used for all elements. Better more than less

.

I use similar constructs as well and I don't think it would be a good idea to exclude everything except simple .class and #id (and element) selectors.

Cheers,
Kybos

notuo · Post by **notuo** » Thu Jun 07, 2007 2:40 pm

Agree.

.foo .bar {}
.foo h2 {}
h3.foo {}

These had to be shown also

Post by **syrupcore** » Thu Jun 07, 2007 7:04 pm

notuo wrote:Agree.

.foo .bar {}
.foo h2 {}
h3.foo {}

These had to be shown also

notuo, kybos - I see your points. This is all only for the sake of discussion as karlis wont be changing it any time soon if ever but in my perfect world...

.foo .bar would only come up as .bar because .bar is the declaration - .foo .bar is only specifying what should happen to .bar when contained within .foo

.foo h2 wouldn't come up at all. the whole reason to use this sort of descendant selector is so you don't have to add it as a class in the html. making an h2 within .foo is all that's needed. plus, it can not apply to anything else you could possibly make in your html.

h3.foo would come up as only .foo. In my crazy perfect world, it would only come up after I typed in class=" on h3 elements.

the .foo h2 is the only one that actually matters to me. I use so many descendant selectors that the help list is full of stuff I can't use.

Will