Tuesday, 29 April 2008
|
| 2 Tableless Three-Column Design Questions Richardv2 06:33:20 |
| | I've set up a three-column tableless site at www.eBookOptions.com. (You
can go there to see what it looks like if you wish.)
Mostly they work as expected except for two things.
My questions... (CSS Code for both below.)
1. Why do I need different "top"s? (leftmenu=135, content=10,
right=135) The tops of these all seem to be 135 pixels from the top of
the page, but I must use "top: 10px;" for the center content column to
work.
2. Left and right stay the same size, and the middle "stretches"
perfectly in all resolutions, EXCEPT there is about a 10px gutter
between the columns. I've tried different numbers and can't get all
three columns to "just touch". What am I doing wrong????
(Comment: I used 1px red, green and blue borders to make it easy to see
and edit. Later I will drop the left and right borders.)
#leftmenu{
border: 1px solid #F00;
padding: 5px;
top: 135px;
position: absolute;
width: 100px;left: 0px;
margin-left: 0px;
margin-right: auto;}
#content{
border: 1px solid #0F0;
padding: 5px;
top: 10px;
position: relative;
margin: 125px 155px 0px 100px;
width: auto;}
#right{
border: 1px solid #00F;
padding: 5px;
top: 135px;
position: absolute;
width: 155px;
right: 0px;
margin-right: 0px;}
|
| Options |  2 answer | Add comment |
Tuesday, 22 April 2008
|
| Question about CSS validation Vlatko Juric-Kokic 21:10:30 |
| | I'm fiddling with some pages and went to see whether the CSS will
validate.
Unfortunately, not.
The validator gives warning "you have no background-color with your
color" for several elements. But I specifically put in
"background-color: transparent", which is allowed/required according
to CSS 2.1:
"background-color
This property sets the background color of an element, either a
<color> value or the keyword 'transparent', to make the underlying
colors shine through."
So why the warning?
I also used the extended file upload interface and told the validator
to use CSS 2.1 but got the same warning.
vlatko
|
| Options | 14 answers | Add comment |
Thursday, 31 May 2007
|
| Input type=file Vishnupriya 09:52:45 |
| | Hi ,
here i am trying to display default value for an input file type.
My code is
<form name="gesimg" action="gesimg.asp" method="post" enctype="multipart/form-data">
<input type="file" name="f" value=""/>
<input
type="submit"
value=""
/>
</form>
but this code is not working can anyone help .
I need to display the value by default path in the file type.
Thanks in advance and I am using IE5.5 .
|
| Options | 3 answer | Add comment |
Thursday, 10 May 2007
|
| Table width Luigi Donatello Asero 12:43:36 |
| | The table with several columns on the page in the signature
seems to be too large at Firefox.
Could I solve the problem by setting the width and forcing the browser to
change the width of each column?
Does that affect the fontsize?
Ps.: is the signature all right now?
--
Luigi Donatello Asero
https://www.scaiecat-spa-gigi.com/sv/boende-i-italien.php
|
| Options | 32 answer | Add comment |
Thursday, 3 May 2007
|
| this needs to be changed in the validator Jasper Magick 06:36:58 |
| |
I see on many many sites, people are serving their documents as
text/html but using the xhtml 1.1 doctype. Yet they don't think
anything about it since the validator says it's valid. Even trying to
contact them letting them know usuaully results in a response like "if
the validator says it's ok, then I'm not changing it"
I think you should add a small modification to the markup validator so
it will call any document with a doctype of xhtml 1.1 and served as
text/html invalid.
|
| Options | 3 answer | Add comment |
Friday, 27 April 2007
|
| CSS 100% height problem Marcel 10:27:40 |
| | I have this CSS HTML page that looks good without content:
http://home.quicknet.nl/qn/prive/n.molenaar/test2/index.html
but when i put content in it problems occur (sidebars are not expanded to
the bottom of the page
http://home.quicknet.nl/qn/prive/n.molenaar/test3/index.html
can someone help?
Marcel
|
| Options | 7 answers | Add comment |
Saturday, 7 April 2007
|
| drop down Kevin Klement 21:36:01 |
| | Afternoon group...
I'm learning drop down menus..
old:
http://www.gypsy-designs.com/credits.html
new:
http://www.gypsy-designs.com/example[2].html
Opinions?
Thanks in advance...
Gufus
mailto:info@gypsy-designs.com
http://www.gypsy-designs.com
... Why glue my bills together? It's a mail bonding ritual.
|
| Options | 136 answers | Add comment |
Thursday, 29 March 2007
|
| classified ads site for Tanzania Guest 08:36:38 |
| | re-posted for a friend (not a usenet person): J's working for a website in Tanzania - a cross between ebay, yellow pages and internet recruitment. The original concept was classifieds, without the bidding of ebay because Tz isn't there yet. It's still that but they also want it to act as an information resources, if you're travelling in Tz and looking for a restaurant or hotel, you can go online and see. Want to sell your car? Put it online. Looking for a volunteer opportunity with an NGO? Have a look at the profiles. Need funding for your NGO, put up a wanted ad. Want to sell your beans and maize from the village to Iringa? Get in touch with someone who can tell you the prices and help you sell them. It's my last day in Iringa, it's 4:30pm and I'm holed up with him in the internet cafe, testing the site. I've been here all day. In an attempt to escape to drink beer, could anyone spend half an hour having a looksee, give him some feedback? Site structure, ease of accessibility, categories. It's all in English and simple by nature, the target group is Swahili speakers and computer sophisitication beyond email, pornography and messenger isn't there.
www.itangaze.com
Email J at jason splodgyatemailthing itangaze.com
|
| Options | 1 answer | Add comment |
Friday, 26 January 2007
|
| XHTML2.0 - transclusion Jakub Dabrowski 00:25:31 |
| | As Object module is responsible for rendering included elements (java,
movies, etc...) - is it also taken into consideration to render any other
inline objects? Eg. inclusions form other documents. The "type" attribute is
to be changed into "srctype" that can be any of defined mime types supported
by browser or its plugins (eg. "application/html+xml", "image/jpeg") which
gives us chance to let "type" define a way that element should be included.
As for now - XHTML is not implementing many of hypertext theories - like
real transclusion.
Translusion in XHTML. Proposal.
Inclusion of other documents or their parts should be allowed. Right now it
is only possible to translude full and complete documents using <iframe>,
<img> (deprecated in XHTML 2.0) and in some cases <object> tags. But idea of
translusions is to allow also parts of remote documents to be included. This
can be achieved in few steps.
1. Document Header.
Author of the document must explicitly allow translclusion of his work. This
may also prevent other documents to include full work (with <iframe> tag).
This can be done with some header tags. Browser must not render content that
is not allowed by author within other document.
2. Document elements
All document elements allowed for translusion should have their own id.
3. Transclusion
Possible for whole (allowed by author) document with <object> tag or for its
parts also with object tag with some parameters.
"type" stands for the way contnt should be rendered: text, xhtml, html,
etc...
3.1 Proposal 1
<!-- remote document.html -->
<p id="myid1">some text</p>
<!-- document with translusion-->
<object src="www.remoteserver.com/document.html"
srctype="application/html+xml" type="plain" transid="myid1">
<em>cannot get content from remote server</em>
</object>
3.2 Proposal 2
<object src="www.remoteserver.com/document.html"
srctype="application/html+xml" type="plain">
<param name="tranid">myid1</param>
<em>cannot get content from remote server</em>
</object>
3.3 Proposal 3
<object src="www.remoteserver.com/document.html#myid1"
srctype="application/html+xml" type="plain">
<em>cannot get content from remote server</em>
</object>
But one <object> cannot transclude another for deadlock prevention.
What do you think?
Regards
Jakub D browski, MSc
|
| Options | 14 answers | Add comment |
Monday, 22 January 2007
|
| [XHTML 2.0] Only one emphasis tag David Latapie 16:33:12 |
| |
(Following the suggestion by Karl Dubost <http://lists.w3.org/
Archives/Public/www-html/2006Sep/0034.html> and its implementation by
Benjamin Hawkes Lewis)
Hi,
This is a comment for "XHTML 2.0"
<http://www.w3.org/TR/2006/WD-xhtml2-20060726/>
2006-07-26
8th WD
Extracted from <http://lists.w3.org/Archives/Public/www-html/2006Sep/
0035.html>
May I please have a tracking of this comment.
About draft generally, but especially <http://www.w3.org/TR/2006/WD-
xhtml2-20060726/mod-text.html#edef_text_em> and <http://www.w3.org/TR/
2006/WD-xhtml2-20060726/mod-text.html#edef_text_strong>
=-=-=-=-=
<em> and <strong> really are just two variations on the same idea,
emphasis. Two tags could be merged as one. Plus, extending the idea
would make possible de-emphasis-like parenthesis, whispering...
My suggestion is " <emph property="numerical value" ".
- <emph> is chosen because it is less ambiguous compared to <em>. On
the other hand, <em> withouth property value set could be a level 1
<em>, like in previous X/HTML version. That would provide a bit of
backward compatibility, with minimal ambiguity.
- values could be like this. Please notice I don't really understand
what role is really meant for
-- <em role="0"> default
-- <em role="+1"> equivalent to em
-- <em role="+2"> equivalent to strong
-- <em role="-1"> less important, may be rendered as font-
size:smaller or voice-stress:reduced <http://www.w3.org/TR/css3-
speech/#voice-stress>
-- and so on
A similar suggestion had been made in June by Jonathan Worent <http://
lists.w3.org/Archives/Public/www-html/2006Sep/0036.html>
--
</david_latapie>
http://blog.empyree.org/ U+0F00
|
| Options | 10 answers | Add comment |
Sunday, 21 January 2007
|
| free imageboard Abracad_1999@Yahoo.Com 20:39:56 |
| | Is there any sites that allow people to set up & run their own
imageboards for free, or alternatively any open source software I can
install on my server to run an imageboard.
|
| Options | 8 answers | Add comment |
Tuesday, 16 January 2007
|
| XHTML and Latest Standards John Goodrich 08:08:25 |
| |
I am new to developing Web pages with HTML, and I'm a bit confused of
where to look for the most current standards. It would be helpful if
the W3C home page simply said somewhere prominently, "The latest
standard for HTML specifications" or something like that. Can someone
just tell me if it is XHTML 1.1, 1.0, XFORMS, XHTML-Print, HTML 4.01, or
what?
J.P. Goodrich
Contractor - Group O Direct
Marketing Support/Services Customer Analytics & ResearchSan Antonio, TX 78205 phone: 210.487.4050CA&R Customer Analytics & Research
|
| Options | 14 answers | Add comment |
Tuesday, 26 December 2006
|
| how is this Strict valid? Jasper Magick 03:49:34 |
| |
According to this:
http://validator.w3.org/check?verbose=1&uri=http%3A%2F%2Fwww.w3.org%2F
w3.org validates Strict. But, in the source code I found this:
<h2 class="newsHeading"><a name="news" id="news" shape="rect">News</a></h2>
I thought NAME was replaced by ID in Strict doctypes, making NAME no longer valid?
Also couldn't you have archived the same effect with less code if you did this:
<h2 class="newsHeading" id="news">News</h2>
|
| Options | 6 answers | Add comment |
Thursday, 21 December 2006
|
| 'dir' attribute on BIDI inline elements and actual browsers Helmut Wollmersdorfer 00:37:32 |
| |
8.2.3 Setting the direction of embedded text
http://www.w3.org/TR/html401/struct/dirlang.html#h-8.2.3
describes the use of the 'dir'-attribute on inline elements, and gives a
nice (and simple) example.
Let me give another example:
<p>English1 <span dir="rtl">עברית2</span>.
<span dir="rtl">עברית3</span> Englisch4.</p>
In plain text
English1 Hebrew2. Hebrew3 English4.
Which some browsers (Mozilla familiy, IE) display
[1] English1 3werbeH .2werbeH English4.
and Konqueror 3.5.5 displays
[2] English1 2werbeH. 3werbeH English4.
Which one is compliant to the W3C Specification?
Or does the specification need corrections,
e.g. 'You need ‎ in such a case'?
Helmut Wollmersdorfer
|
| Options | 8 answers | Add comment |
Friday, 15 December 2006
|
| Location of Relax NG files for XHTML 2? Peter Krantz 14:34:50 |
| |
Hi!
I am trying out some sample documents in XHTML 2 that I would like to
check with the Relax NG schema available at the W3C website [1].
Where can I find the actual Relax NG files? After some digging I found
[2] but those files seem to be older than what is available at [1]?
Should I copy and paste the Relax NG source from the HTML pages at [1]
to get the latest version?
Regards,
Peter
[1] http://www.w3.org/TR/xhtml2/xhtml20_relax.html#a_xhtml20_relaxng
[2] http://www.w3.org/MarkUp/RELAXNG/
|
| Options | 1 answer | Add comment |
Wednesday, 6 December 2006
|
| XHTML 1.0 served as text/html Philip TAYLOR 23:03:14 |
| |
Forgive the multiplicity of named recipients, but
I am very uncertain as to whom to address this :
There has been a fairly protracted discussion recently
concerning the pros and cons of serving XHTML documents
as text/html or as application/xhtml+xml, but I was more
than a little surprised today to discover that when the
W3C (HTML) validator is asked to validate
http://www.isg.rhul.ac.uk/
it states that the (page) is "Valid XHTML 1.0 Transitional"
without issuing even a warning that it is being served as
text/html rather than application/xhtml+xml. Now it is
clear from Section 5.1 of
http://www.w3.org/TR/xhtml1/
that this is acceptable, yet
http://www.w3.org/TR/xhtml-media-types/
also states clearly that
"application/xhtml+xml SHOULD be used for XHTML Family documents"
My question is therefore : should not the validator issue
a warning when this last guideline is ignored ?
Philip Taylor
|
| Options | 11 answers | Add comment |
Saturday, 2 December 2006
|
| XHTML 1.0, section C14 David Dorward 00:31:40 |
| |
I've got a few questions about Appendix C.
Why is section C14 "Referencing Style Elements when serving as XML"
part of Appendix C "HTML Compatibility Guidelines"?
My understanding is that
<?xml-stylesheet href="#internalStyle" type="text/css"?>
is an XML processing instruction. Is this right? If so, why does C14
seem to contradict section C1 (which advises against using XML
processing instructions) by requiring processing instructions?
Why does it require a processing instruction for <style> elements, but
not <link> elements with rel="stylesheet"?
--
David Dorward http://dorward.me.uk
|
| Options | 32 answer | Add comment |
Tuesday, 28 November 2006
|
| Baseline of OBJECT and supported media types Mikko Rantalainen 18:12:42 |
| |
[was: Re: XHTML 1.0, section C14]
Benjamin Hawkes-Lewis wrote: On Tue, 2006-11-28 at 15:58 +0200, Mikko Rantalainen wrote: Is there a way to get correct baseline alignment when MathML is placed inside an OBJECT? Yes, it's possible to get somewhat acceptable result but HTML+OBJECT isn't a substitute for XHTML+MathML. I tried Googling for the problem you refer to, but couldn't find anything. Do you have a link or example of a baseline problem in OBJECT?
If you want to insert something like a^sqrt(2) inlined there isn't a
nice way to get baseline of letter "a" (practically the bottom of
letter "a") at the same height as baseline of the text line.
(the a^sqrt(2) is short for a to power of square root of 2)
The problem is that you cannot (AFAIK) tell OBJECT to position the
letter "a" inside the OBJECT at the height a normal letter "a" would
be positioned if OBJECT were replaced with just a letter "a". See
any math book for an example. I would expect a normal UA to send list of media types it "supports" in its normal Accept header but there could be an UI to fetch the "source" version of the document where the UA would repeat the request without Accept header (or with Accept: */*). Sorry, Mikko, I'm still not clear what you mean by "supports". And would you mind elaborating on how such a user interface might work and what it might look like in practice (from the end-user's perspective I mean)?
I guess an UA should define what "supports" means. I would like if
it meant "every MIME type the system is able to present". Such an
Accept header would be too long for real world usage, though.
Perhaps "supports" should be defined as "every MIME type that can be
presented within the UI of UA". For visual UAs that would mean "all
native media types of UA plus all MIME types supported by plugins",
I guess.
As for the UI, I'd suggest something similar as current visual UAs
have for "Save link target as..." action (usually in the context
menu of a link). It would make sense to save the "best" format if I
store the target of the link without viewing it. I can always save
the version I'm currently seeing with other means (usually in menu
File - Save as...).
--
Mikko
|
| Options | Add comment |
|
| Broken DTD for XHTML 1.1 Benjamin Hawkes-Lewis 15:57:28 |
| |
The XHTML 1.1 DTD references
http://www.w3.org/TR/xhtml-modularization/DTD/xhtml11-model-1.mod
But this URI results in a 404, which causes XML parsers that actually
read the DTD to fail. Where did it go to? And can we have it back? ;)
--
Benjamin Hawkes-Lewis
|
| Options | 4 answer | Add comment |
Saturday, 25 November 2006
|
| [XHTML-role] How to define roles still needs clarification Benjamin Hawkes-Lewis 20:20:38 |
| |
Hi
This is a comment for "XHTML Role Attribute Module"
http://www.w3.org/TR/2006/WD-xhtml-role-20061113
2006-11-13
Working Draft
Re: Note that current best practice is that the URI associated with that namespace resolve to a resource that allows for the discovery of the definition of the roles in the namespace.
As I suggested back in September,
http://lists.w3.org/Archives/Public/www-html/2006Sep/0030.html
Surely it should be an *absolute and fundamental requirement* (not
merely "best practice") for "the URI associated with" a role's namespace
to "resolve to a resource that allows for the discovery of the
definition of the roles in the namespace" so that user agents can always
learn new roles?
Re: User agents, search engines, etc. may interpret these relationships in a variety of ways
If browsers are to learn new roles, should it not be an absolute
requirement for role definitions to include machine-understandable
suggestions on how to interpret and render such relationships, aurally
and visually?
Should it not also be an absolute requirement for role definitions to
include a machine-understandable specification of whether the defined
relationships are:
1. Of primary importance and must be obviously exposed to end-users
(like ordinary hyperlinks).
2. Only of secondary importance, with access dependent on end-users
requesting more information (like the TITLE attribute in HTML4).
3. Unimportant to end-users (like the CLASS attribute in HTML4).
Should such styling and behaviours be entirely dependent on (potentially
disabled) stylesheets and scripting, and does that conflict with
accessibility requirements? This must be clarified.
Bear in mind, when considering this question, the example of the radical
difference in treatment by current browsers between the HREF attribute
of LINK, the HREF attribute of A, and the under-appreciated CITE
attribute of INS, DEL, Q, and BLOCKQUOTE in HTML 4.01. No rendering was
suggested and no importance was specified for CITE, and it has been
mostly ignored, undermining its potential to extend hypertext in
interesting ways.
(I'm cross-posting to the www-html list for discussion.)
--
Benjamin Hawkes-Lewis
|
| Options | 4 answer | Add comment |
Wednesday, 22 November 2006
|
| Defining processing of invalid documents (Was: Charters for review (TAG issue tagSoupIntegration-54) Ian Hickson 00:30:25 |
| |
(Thread moved to www-html@w3.org at danc's request.)
Ed Rice <ed.rice@hp.com> wrote, on w3c-html-cg@w3.org: Doesn't including the non-well-formed/invalid documents in the architecture/design actually validate the design and say that there is no such thing as a non-well-formed document?
No; you can simultaneously say that something is invalid and say exactly
how it should be processed. CSS does this; for instance:
p { color: "red"; color: green; }
...is completely invalid CSS (you can't pass a string to the property
'color'), but every conforming UA will handle it the same.
In the case of HTML5, the HTML5 parser spec:
http://whatwg.org/specs/web-apps/current-work/#parser
...defines what is an error (non-conforming syntax) and what isn't.
HTH,
--
Ian Hickson
|
| Options | Add comment |
Tuesday, 21 November 2006
|
| Re: [WebAIM] More data on accesskeys (New article written Nov. 1) David Woolley 10:55:17 |
| | Could we use a link in the head that goes to a static (cacheable) file for site-wide navigation? I know you could use a server side include, but it seems kludgy, as you are still sending (potentially) quite a lot
I believe this is what the purpose of several of the original link
types was, and to me it would be much cleaner than duplicating
menus on every page. There are at least 2 major problems with using technique like that. 1. Backwards compatibility. 2. Such a major conceptual change in the way pages are linked is unlikely to catch on significantly in the real world.
3. I would result in uniform behaviour (for a single browser) across
sites, which would be rejected by designers because it frustrated
branding.
|
| Options | Add comment |
Tuesday, 14 November 2006
|
| About XHTML2 and IE7 Jasper Magick 01:19:16 |
| |
With Microsoft's decision not to support application/xhtml+xml (even
after promising they would, those fools) will XHTML 2.0 be harder to
"promote".
http://blogs.msdn.com/ie/archive/2005/09/15/467901.aspx
Won't IE7's lack of the right content type mean almost no one will want
to use XHTML 2.0 since about 70-80% of Internet users use IE?
|
| Options | 6 answers | Add comment |
Tuesday, 7 November 2006
|
| HTML 4.01: Char encoding defaults for external scripts? Claudio Pellegrino 13:20:33 |
| |
Hello,
I have a small problem with interpreting part of the HTML 4.01 specs.
It is about character encoding assumptions from the user agent point
of view.
Assume the following scenario:
1. Let doc.html be an HTML 4.01 document served as "text/html".
2. The content of doc.html is encoded with UTF-8, and
the meta element declaration correctly says so.
3. The document also contains a "script" element having
type="text/javascript" and src="ext.js", but no
"charset" attribute.
4. The HTTP server does not serve a "charset" header,
neither for "doc.html" nor for "ext.js".
Given the above scenario, here are my two questions:
According to the HTML 4.01 specs, is the user agent
a) *required* to assume a specific character encoding
for the content of "ext.js"? If so, which one and
why?
b) *allowed* to ignore the list of three encoding
priorities at [2] and use heuristics instead
for determining the content encoding of "ext.js"?
Some reasons why I'm clueless about it:
- The "script" element specification [1] doesn't
specify a default behaviour for the user agent.
- The page about encodings [2] cites a list of three
encodings which may be applicable for "doc.html" -
but not necessarily for "ext.js" since the page
only mentions the "document's character encoding".
- The "charset" attribute description [3] doesn't
specify any implied default value or behaviour.
- I see similar problems in XHTML 1.0 [4].
- I feel I have checked with the appropriate sources,
including all the links within [5] and, of course,
the list archive, but found little more than
authoring advice ...
Is there a part of the specs I have missed?
Any pointer would be appreciated. Thanks a lot!
Regards,
Claudio Pellegrino
[1] http://www.w3.org/TR/html4/interact/scripts.html#h-18.2.1
[2] http://www.w3.org/TR/html4/charset.html#h-5.2.2
[3] http://www.w3.org/TR/html4/struct/links.html#adef-charset
[4] http://www.w3.org/TR/xhtml1/#C_9
[5] http://www.w3.org/International/articles/#chars
|
| Options | 7 answers | Add comment |
Monday, 6 November 2006
|
| (Solution) HTML 4.01: Char encoding defaults for external scripts? Claudio Pellegrino 11:50:45 |
| |
Hello,
[original scenario] 1. Let doc.html be an HTML 4.01 document served as "text/html". 2. The content of doc.html is encoded with UTF-8, and the meta element declaration correctly says so. 3. The document also contains a "script" element having type="text/javascri pt" and src="ext.js", but no "charset" attribute. 4. The HTTP server does not serve a "charset" header, neither for "doc.html" nor for " ext.js".
Thanks to James Justin's answer, I see a possible explanation now.
I'll try to sum it up myself:
- Authoring a script ref. to a non-US-ASCII external resource REQUIRES
the author to specify a charset (as RFC 2046 demands). This can be
done either way: embedded in the "type" attribute or by specifying
a separate "charset" attribute within the script element.
- In particular, declaring a character encoding *for the
entire document* is not sufficient to fulfill the above requirement.
User agents are not REQUIRED to propagate, for example, a charset
declaration given in the META element all the way down to the content
of the external script resource.
- However, the user agent MAY take the document encoding (e. g. from the
META element) as a fallback/hint. It seems to me that most
(but not all) popular browsers do exactly that.
(This is what actually raised my question in the first place.)
- Lesson learned: Given the scenario, the user agent behaviour
is not specified according to HTML 4.01.
I hope this explanation is roughly correct.
Regards
Claudio Pellegrino
|
| Options | Add comment |
|
