Re: [WSG] position fixed on the thead
I came up with a solution for this exact problem a while back and wrote about it here http://www.agavegroup.com/?p=31 It relies on only one extra div, then a className. I often load the table normally, then onLoad, apply the classname to the table which resets it to being scrollable. Hope it helps.On 11/7/05, Ted Drake [EMAIL PROTECTED] wrote: This solution is really cool. The programmer is simply putting the thead andtfoot outside a scrolling div with absolute positioning. The tbody is allthat is left in the div and it scrolls. http://web.tampabay.rr.com/bmerkey/examples/nonscroll-table-header2.htmlThanks Scott for finding it.Ted-Original Message-Hi TedIn response to: I'd like to keep the thead fixed and let the remainder of the rows scroll underneath it.I came across thishttp://web.tampabay.rr.com/bmerkey/examples/nonscroll-table-header2.html while scouring the web for fixed print header/footer solutions. It seems tofit your requirements, though I haven't investigated/played with it myself.RegardsScott Swabey** The discussion list forhttp://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help**-- www.agavegroup.com
Re: [WSG] Friday fun with Suckerfish dropdowns
Which part are you trying to right align?
If you want the whole thing on the right, you can put float the
top-left UL to the right:
ul{
float:right;
}
If you want to get the menu items, you can align the text in both LIs
li{
text-align:right;
}
On 8/25/05, Miles Tillinger [EMAIL PROTECTED] wrote:
Has anyone been able to successfully right align the Suckerfish
horizontal dropdown menu without defining the width of the container or
UL? Preferably would work in Opera and Mac IE5 if possible.
I am using the following example:
http://www.htmldog.com/articles/suckerfish/bones/
MT.
**
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list getting help
**
--
www.agavegroup.com
**
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list getting help
**
Re: [WSG] Help with a simple (?) problem
One step further, just add this:
html, body{
height:100%;
}
Remember that HTMLand BODY are valid elements that wrap all of your
content. To varying extents they can be styled like any other element
on your page. In firefox, HTML and BODY inherit their height and
width from the browser window itself, while in IE, the width is
inherited, but not the height (go figure). So setting them both to
100% height gets things consistent across browsers.
On 8/19/05, alejandro poch [EMAIL PROTECTED] wrote:
Hi man
Just try to write
height: 100%;
on the BODY on the css file and you're done. At least it work for me.
Christian Robertson wrote:
Hi all,
I am new to the list, and this is my first posting so please be gentle ;-)
I have a task I am trying to accomplish which is not going to plan.
The base code for what I want to achieve can be found at:
http://www.metamorphosis.info/test/index-test.htm
My aim is to place a single blue panel 300px from the left of the
screen, and for it to stretch from the top to the bottom. Within
that, I would like a content container element, beginning 200px from
the top.
The result is achieved by the code below in Firefox, but IE will not
stretch the pale blue background from top to bottom - seems to fit it
to the content. I've tried many options, but without success.
Can anyone please put me on the right track? Apologies if the solution
is simple, but it's often the simple plans which tend to be overlooked.
Many thanks in advance.
Chris
*XHTML:*
body
div id=maincol
div id=container
pPara 1 .../p
pPara 2 .../p
/div
/div
/body
/html
*CSS:*
body {
background-color: #909fb2;
margin: 0;}/* body margin set to 38
at top - impacts placement */
#maincol {
position: absolute;
left: 300px;
width: 270px;
height: 100%;
background-color: #b1bbc8;}
#container {
position: relative;
top: 200px;
width: 268px;
border: 1px solid #fff;
background-color: #b1bbc8;}
**
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list getting help
**
--
www.agavegroup.com
**
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list getting help
**
Re: [WSG] Need recomendations for CMS system
Based on your requirements, I'd say your choices are Textpattern or Wordpress. I built my site on wordpress(http://www.agavegroup.com) and after that experience (and installing both wordpress and textpattern) I'd say Wordpress is easier to use, and is a great choice for small to medium sites. Anything bigger I think I'd choose Textpattern. While not quite as straight forward (in my opinion) it seems to extend into the CMS world a little better. ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] FireFox DOM issue.
In firefox, I have had success with selectionStart and selectionEnd
if you have a form:
form name=a
textarea name=b/textarea
you can access the start and end points of the highlighted text (or
get the position of the cursor in the text) with:
startPoint = document.a.b.selectionStart;
endPoint = document.a.b.selectionEnd;
This won't work in IE (where I tend to use document.selection) so you
have to do some kind of functionality test like:
if(document.selection){
//do IE stuff
}else if(myField.selectionStart)
//do mozilla stuff
Hope this helps
--
Patrick
www.agavegroup.com
On 8/9/05, Buddy Quaid [EMAIL PROTECTED] wrote:
Hi everyone,
I'm new to this group and this is my first message.
I am porting over a rich text editor that currently only works in IE.
I have done tons of search about getting the selected text in a page.
I'm very close...for instance...you can now see the formatting buttons
and also I have the correct code to get it to know what is selected and
if you click 'bold' it will put the bold tags around it in a text box.
I want it so that if NOTHING is selected and you hit bold it will give
you an alert box for the text that you would like bolded. Then plance
that text with the bold tags around it. My problem is I can't get the
right code of the DOM to test correctly for a selection being made in
the text box.
I am currently trying
Str = window.getSelection;
If (str.isCollapsed) {
if true do this;
}else{
do this;
}
I put alert(str.isCollapsed) in there to trace what is going on but it's
ALWAYS true.
I'm wondering if it's because the text is in a textarea and not just on
the page?
Like I said, I have been getting it to work without sniffing to see if a
selection has actually been made to put the tags around the text but I
can't for the life of me sniff it out through code.
I've also tried
Str = window.getSelection;
If(str.toString().length 0) to no avail.
Thanks in advance!
Buddy
**
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list getting help
**
**
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list getting help
**
[WSG] Firefox DOM and whitespace (bug?)
I recently ran across an issue (I would call it a bug?) in firefox's DOM. I wrote a rather lengthy bit on it here: http://www.agavegroup.com/?p=32 But in short, firefox considers whitespace (tab, space, new line) to be nodes in the DOM. I've browsed the W3C spec, as well as the Mozilla DOM spec and I can't come up with anything that demonstrates how this should be handled. But it seems to me white space should be entirely ignored in the DOM. I just wanted to see if anyone else has run into this, and hear some thoughts. IE handles this differently (no surprise there...) and in this case, better. Is this a recent Firefox bug or proper behavior (that must be scripted around...). I'd be interested in any other thoughts/ideas. Thanks, Patrick ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] Firefox DOM and whitespace (bug?)
Thank you for the excellent reponses. I can't believed I missed the whitespace document (http://www.mozilla.org/docs/dom/technote/whitespace/) I see the point, and from a one standard fits all perspective, it makes good sense. I do have to wonder though: The point of defining a DOM is to give you a structure to work with. And it's OK to create sort of sub DOMs. For example the XML DOM is basically a child of the SGML DOM. In other words while standard, the DOM was changed for XML (and therefore XHTML) to better suit XML. User agents have always (and will always) ignore whitespace in their display of XHTML. Should the DOM ignore it too? I recognize that's kind of backward logic, but it's certainly the practical view. Anyway, as they say - learn something new every day. Thanks for the reponses. -- Patrick Ryan http://www.agavegroup.com On 8/4/05, Ben Curtis [EMAIL PROTECTED] wrote: On Aug 4, 2005, at 1:39 PM, Patrick Ryan wrote: I recently ran across an issue (I would call it a bug?) in firefox's DOM. ... But in short, firefox considers whitespace (tab, space, new line) to be nodes in the DOM. ... But it seems to me white space should be entirely ignored in the DOM. ... IE handles this differently (no surprise there...) and in this case, better. Is this a recent Firefox bug or proper behavior (that must be scripted around...). Firefox is right, I believe, because the DOM is defined like this: The DOM presents documents as a hierarchy of Node objects that also implement other, more specialized interfaces.[1] The whitespace is part of the document, therefore the DOM must present it within the hierarchy of Nodes. In this case, it is a Text node (defined on the same page). The proper way to parse a Nodelist is to not assume you know what is next, but to test what Nodetype the next child is, and then tailor your operation to fit (e.g., skip the whitespace and gimme the next node). Admittedly, the IE model would make some of my scripts easier to write, but then we'd lose the capability of the DOM to work with XML such that *everything* is a node, and HTML would be a special case that ignores whitespace. Enough special cases, and the standard ain't so standard. So I think we need to keep coding with tests for Nodetype. 1. http://www.w3.org/TR/DOM-Level-2-Core/core.html -- Ben Curtis : webwright bivia : a personal web studio http://www.bivia.com v: (818) 507-6613 ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
