Hi WSG'ers
After seeing Sarah's post about CSS for titles, I thought that people
might be interested in this idea. It's a half baked idea. If you have
any comments or suggestions, I would love to hear them.
Apologies for those who have already seen this on the DC-General list.
** The
Folks,
Any of you that remember when this list server took commands via email,
please forget it ever happened.
The only way to edit your setting is to log in and set them on the website.
Even if you do manage to get a command to work, the next time the system
writes the subscription file from
Jonathan O'Donnell wrote:
meta name=DC.title content=#title /
meta name=DC.creator content=#creator /
meta name=DC.creator content=#rights /
I'm not a DC expert, but I believe that that's not a valid way to go
about it. When you embed DC information via meta elements, content
sites need to be aesthetically pleasing as well as accessible and CSS
and DOM scripting gives us more than enough power to do
both.
agreed,
It
would be hard to get customer sign off on such adesign,
even
soits quick loading and accessible.
Perhaps you could sit down with a graphic
Hi Jonathan,
I second Patrick's comment that 'pointing' the DC records to content on the
page is not the solution.
Although, from a maintenance perspective, this may appear to be a work-around
for not completing the metadata records (questionable), metadata harvesting
tools are unlikely to
Hi Sarah,
I was just looking for a way to give the user immediate feedback about
each reference, and thought the title may be useful.
The problem with linking back and forth is that there are *so* many
references on each page, sometimes two or three to each quote, so it
gets a bit messy.
Title: Message
I have a problem in
firefox where it displays a white area where there should not be
one.
http://www.ozblackberry.com/index.cfm
is fine, simply because I put a 1px white border around the #content_text, but
if I remove that and look at
Taco Fleur - Pacific Fox wrote:
I have a problem in firefox where it displays a white area where
there should not be one.
http://www.ozblackberry.com/index.cfm is fine, simply because I put a
1px white border around the #content_text, but if I remove that and
look at
Apologies if this has been discussed before, but is it my bad coding,
or does Safari (v2.02, latest build) not honour any select styles?
Further, is there a way to dictate how option can display styled
font attributes across all CSS-compliant browsers? My aim is to make
the drop-down in the same
Jonathan O'Donnell wrote:
Hi WSG'ers
In general, data (including metadata) should be stored in one place
only. This prevents drift: if it is only stored in one place, it can
only be updated in that place.
Often, the information that we want to store as metadata already
appears in the Web
Hi,
Thanks for the reply.
I'm a bit uneasy about this. I don't want a border, and I certainly don't
want 0 margin on my paragraph elements, isn't there another solution?
Thanks,
Taco Fleur - CEO
Pacific Fox http://www.pacificfox.com.au
an industry leader with commercial IT experience since
OK, so I added a border at the top of 1px and added a negative margin of
1px, this seems to solve it, thanks.
Any idea on the other problem with the ol list?
thanks
Taco Fleur - CEO
Pacific Fox http://www.pacificfox.com.au
an industry leader with commercial IT experience since 1994
** Web
On 6 Nov 2005, at 10:54 am, ivanovitch wrote:
Apologies if this has been discussed before, but is it my bad coding,
or does Safari (v2.02, latest build) not honour any select styles?
Further, is there a way to dictate how option can display styled
font attributes across all CSS-compliant
Taco Fleur - Pacific Fox wrote:
I'm a bit uneasy about this. I don't want a border, and I certainly
don't want 0 margin on my paragraph elements, isn't there another
solution?
As mentioned earlier...
#content_text {padding: 1px 0;}
...will solve it.
Georg
--
http://www.gunlaug.no
Thanks, Philippe - I was hoping that I'd hear otherwise. I'm not
attempting to make radical changes to the user interface: just aiming
for consistency. Interesting that certain widgets are off-limits in
this sense, yet submit can be OS-built, text, or image. I had
considered using dropdown menu
Hi Andy
Thank you for your input.
Unfortunately the exact wording of the content (in this client's case)
is legally required, and so the possibility of editing it, or the
references, in any way is out of the question.
I like the idea of linking back to the content once the reader has read
the
G'day
I like the idea of linking back to the content once the reader has read
the relevant footnote, but there are many instances when more than one
footnote is attributed to a portion of the content (see example below).
Also, the same footnote reference is referred to in different portions
of
Hi Sarah,
Unfortunately the exact wording of the content (in this client's case)
is legally required, and so the possibility of editing it, or the
references, in any way is out of the question.
Moving the title of the reference to the fore of the title attribute value
wouldn't be changing the
Hello all. I was thinking about a semantic way to do the following with a list:
= header
- item 1
- item 2
- item 3
Currently I do this:
h1header/h1
ul
li.../li
/ul
This doesn't make it clear that the header refers to the list, though.
What I would like to do is have a list header, much like
19 matches
Mail list logo
