00:00:00 --- log: started forth/07.02.12 00:00:08 --- join: arke_ (n=chris@pD9E07B73.dip.t-dialin.net) joined #forth 00:07:17 --- join: ecraven (n=nex@eutyche.swe.uni-linz.ac.at) joined #forth 00:16:47 --- quit: arke (Read error: 110 (Connection timed out)) 00:25:27 --- join: Raystm2- (n=NanRay@adsl-69-149-62-115.dsl.rcsntx.swbell.net) joined #forth 00:25:47 --- quit: cmeme ("Client terminated by server") 00:26:23 --- join: cmeme (n=cmeme@boa.b9.com) joined #forth 00:32:30 --- quit: Raystm2 (zelazny.freenode.net irc.freenode.net) 00:33:44 --- join: Raystm2 (n=NanRay@adsl-69-149-62-115.dsl.rcsntx.swbell.net) joined #forth 00:41:21 --- join: Raystm2_ (n=NanRay@adsl-69-149-41-226.dsl.rcsntx.swbell.net) joined #forth 00:43:27 --- quit: Raystm2 (Read error: 113 (No route to host)) 00:52:41 --- quit: Crest (Read error: 145 (Connection timed out)) 00:53:26 --- join: Crest (n=crest@p548955E0.dip.t-dialin.net) joined #forth 00:56:35 --- quit: Raystm2- (Read error: 110 (Connection timed out)) 03:12:48 --- join: Zarutian_ (n=Zarutian@194-144-84-110.du.xdsl.is) joined #forth 03:12:49 --- quit: Zarutian (Read error: 104 (Connection reset by peer)) 03:30:30 --- join: tathi (n=josh@pdpc/supporter/bronze/tathi) joined #forth 03:30:30 --- mode: ChanServ set +o tathi 04:36:17 --- nick: Zarutian_ -> Zarutian 04:51:02 --- join: Zarutian_ (n=Zarutian@194-144-84-110.du.xdsl.is) joined #forth 04:51:33 --- quit: Zarutian (Read error: 104 (Connection reset by peer)) 05:03:07 --- quit: Zarutian_ (Read error: 104 (Connection reset by peer)) 05:05:04 --- join: Zarutian (n=Zarutian@194-144-84-110.du.xdsl.is) joined #forth 05:56:19 --- join: timlarson_ (n=timlarso@65.116.199.19) joined #forth 06:13:56 hey 06:13:59 --- quit: Raystm2_ (Read error: 110 (Connection timed out)) 06:16:28 hey 06:22:05 I was reading the draft ANS spec, and found something which puzzled me in A.6.1.2250 STATE. 06:22:46 : NOP : POSTPONE ; IMMEDIATE ; 06:22:46 NOP ALIGN NOP ALIGNED 06:22:46 Some non-ANS Forth compliant systems have ] invoke a compiler loop in addition to setting 06:22:49 STATE. Such a system would inappropriately attempt to compile the second use of NOP. 06:23:53 I don't understand that at all. Surely in such a system [ would exit the compiler loop, and hence it would work just fine. 06:46:59 --- join: Raystm2 (n=NanRay@adsl-68-95-253-147.dsl.rcsntx.swbell.net) joined #forth 06:47:17 --- quit: ecraven ("bbl") 06:49:26 --- join: Raystm2- (n=NanRay@adsl-68-95-253-147.dsl.rcsntx.swbell.net) joined #forth 07:05:12 --- quit: Raystm2 (Read error: 110 (Connection timed out)) 07:10:53 --- quit: Quartus_ (Read error: 104 (Connection reset by peer)) 07:23:49 --- join: Zarutian_ (n=Zarutian@194-144-84-110.du.xdsl.is) joined #forth 07:23:49 --- quit: Zarutian (Read error: 104 (Connection reset by peer)) 07:27:42 --- nick: arke_ -> arke 07:27:43 --- mode: ChanServ set +o arke 07:28:42 --- quit: Raystm2- ("Should have paid the bill.") 07:29:21 --- join: Raystm2 (n=NanRay@adsl-68-95-253-147.dsl.rcsntx.swbell.net) joined #forth 07:51:20 --- quit: tathi (zelazny.freenode.net irc.freenode.net) 07:51:20 --- quit: arke (zelazny.freenode.net irc.freenode.net) 07:51:20 --- quit: crc (zelazny.freenode.net irc.freenode.net) 07:51:21 --- quit: TreyB (zelazny.freenode.net irc.freenode.net) 07:53:45 --- quit: Raystm2 ("Should have paid the bill.") 07:55:16 --- join: arke (n=chris@pD9E07B73.dip.t-dialin.net) joined #forth 07:55:16 --- mode: ChanServ set +o arke 07:57:17 --- join: tathi (n=josh@pdpc/supporter/bronze/tathi) joined #forth 07:57:17 --- mode: ChanServ set +o tathi 07:57:22 --- join: TreyB (n=trey@cpe-66-87-192-27.tx.sprintbbd.net) joined #forth 08:01:15 --- join: crc (n=crc@pdpc/supporter/active/crc) joined #forth 08:01:15 --- mode: irc.freenode.net set +o crc 08:05:51 --- join: Raystm2 (n=NanRay@adsl-68-95-253-147.dsl.rcsntx.swbell.net) joined #forth 08:17:45 --- join: timlarson__ (n=timlarso@65.116.199.19) joined #forth 08:19:04 --- join: timlarson___ (n=timlarso@65.116.199.19) joined #forth 08:35:24 --- quit: timlarson_ (Read error: 110 (Connection timed out)) 08:35:27 --- quit: Zarutian_ (Read error: 104 (Connection reset by peer)) 08:36:11 --- quit: timlarson__ (Read error: 110 (Connection timed out)) 08:39:09 --- join: Zarutian (n=Zarutian@194-144-84-110.du.xdsl.is) joined #forth 09:21:20 --- join: timlarson__ (n=timlarso@65.116.199.19) joined #forth 09:29:10 --- join: Quartus_ (n=Quartus_@209.167.5.1) joined #forth 09:29:10 --- mode: ChanServ set +o Quartus_ 09:33:37 hi ho 09:39:32 --- quit: timlarson___ (Read error: 110 (Connection timed out)) 09:54:19 --- join: ikaros (n=ikaros@p54A7D389.dip.t-dialin.net) joined #forth 10:04:32 --- join: Zarutian_ (n=Zarutian@194-144-84-110.du.xdsl.is) joined #forth 10:06:07 --- quit: Zarutian (Read error: 104 (Connection reset by peer)) 10:12:08 --- part: ikaros left #forth 10:27:44 --- join: virl (n=virl@chello062178085149.1.12.vie.surfer.at) joined #forth 10:35:56 --- quit: Quartus_ (Read error: 104 (Connection reset by peer)) 11:12:39 --- quit: tathi ("leaving") 11:23:13 --- join: timlarson___ (n=timlarso@65.116.199.19) joined #forth 11:34:29 --- quit: Snoopy42 () 11:35:50 --- join: Snoopy42 (i=snoopy_1@dslb-084-058-152-112.pools.arcor-ip.net) joined #forth 11:37:37 --- join: timlarson_ (n=timlarso@65.116.199.19) joined #forth 11:41:13 --- quit: timlarson__ (Read error: 110 (Connection timed out)) 12:05:07 --- quit: timlarson___ (Read error: 110 (Connection timed out)) 12:34:07 --- quit: timlarson_ (Read error: 104 (Connection reset by peer)) 12:34:23 --- join: timlarson__ (n=timlarso@65.116.199.19) joined #forth 12:46:11 --- join: timlarson___ (n=timlarso@65.116.199.19) joined #forth 12:50:13 --- join: tathi (n=josh@pdpc/supporter/bronze/tathi) joined #forth 12:50:13 --- mode: ChanServ set +o tathi 13:01:17 --- join: grub_booter (n=charlie@d54C37C64.access.telenet.be) joined #forth 13:02:40 --- quit: timlarson__ (Read error: 110 (Connection timed out)) 13:18:37 --- quit: timlarson___ ("Leaving") 13:35:42 --- quit: grub_booter (Read error: 104 (Connection reset by peer)) 13:48:12 --- join: Quartus_ (n=Quartus_@209.167.5.1) joined #forth 13:48:12 --- mode: ChanServ set +o Quartus_ 14:27:57 --- quit: tathi ("installing Source Mage") 14:41:10 good evening 14:45:17 --- quit: Quartus_ (Read error: 104 (Connection reset by peer)) 14:51:04 --- join: Quartus_ (n=Quartus_@209.167.5.2) joined #forth 14:51:04 --- mode: ChanServ set +o Quartus_ 15:05:46 --- join: grub_booter (n=charlie@d5152D937.access.telenet.be) joined #forth 15:15:43 --- quit: grub_booter (Read error: 104 (Connection reset by peer)) 15:19:45 --- join: grub_booter (n=charlie@d5152D937.access.telenet.be) joined #forth 15:20:22 sorry for all the to and fro'ing - my connection has been screwy over the past few days 15:20:55 no biggie 15:21:07 it is for me :-/ 15:21:45 getting an average connection time of about 30 minutes before the damn thing drops... impossible to have chat conversations this way 15:22:27 had it before - normally fixed by just bouncing the cable modem and router - not this time though 15:24:08 if anyone has another suggestion, i'd be happy to hear it :-) (unless it's 'change isp' - there's not much choice here..) 15:24:20 call in 15:24:33 yeah - guess so 15:30:32 --- quit: grub_booter (Read error: 104 (Connection reset by peer)) 15:46:34 --- join: grub_booter (n=charlie@d5152D937.access.telenet.be) joined #forth 15:46:57 * grub_booter sighs 15:52:09 holy crap 15:52:15 just learned something about css 15:52:23 this has been killing me for ages 15:54:33 what? 15:54:36
foo
15:55:36 if there's no padding-top or border-top on the parent element, then it's margin-top becomes the max of it's margin-top and the first inner element's margin-top 15:55:54 so in the example above, there's a huge padding above where the background image shows 15:56:18 ie that margin is not inside the parent element at all 15:56:54 --- nick: JasonWoo1 -> JasonWoof 15:57:02 --- mode: ChanServ set +o JasonWoof 15:57:49 simpler example:
foo
15:58:54 that's pretty odd... 15:59:33 yes 15:59:41 and stupid, and irritating 16:00:02 so it's not possible to have a margin inside the parent box 16:00:09 --- nick: Zarutian_ -> Zarutian 16:00:43 suppose they intended "padding" for this purpose 16:00:56 except IE gets the width wrong if you specify padding 16:01:17 16:02:01 at least I figured out why it's putting margins on things where I specified margin: 0px 16:18:02 --- quit: arke ("Konversation terminated!") 16:22:18 --- join: arke (n=chris@pD9E07B73.dip.t-dialin.net) joined #forth 16:22:18 --- mode: ChanServ set +o arke 16:55:21 ah,you kids, with your CSS, and your grunge, and your Wiis, and your Beck 16:56:58 --- join: Zarutian_ (n=Zarutian@194-144-84-110.du.xdsl.is) joined #forth 16:59:19 --- quit: Zarutian_ (Read error: 104 (Connection reset by peer)) 17:00:12 --- quit: Zarutian (Read error: 104 (Connection reset by peer)) 18:54:02 --- join: tathi (n=josh@pdpc/supporter/bronze/tathi) joined #forth 18:54:03 --- mode: ChanServ set +o tathi 19:13:38 --- join: nighty^ (n=nighty@sushi.rural-networks.com) joined #forth 19:24:12 ok, here's an even better example:
foo
19:24:35 You'd think that would display a huge red filled rectangle with a small blue one inside 19:24:52 instead it displays a thin blue stripe that is red on the left and right ends 19:25:08 which is 200px down the page 20:23:55 --- quit: Snoopy42 () 20:25:58 --- join: Snoopy42 (i=snoopy_1@dslb-084-058-152-112.pools.arcor-ip.net) joined #forth 20:30:18 --- quit: nighty^ (Remote closed the connection) 22:23:57 --- quit: virl ("Verlassend") 22:27:38 --- join: slava (n=slava@CPE0080ad77a020-CM000e5cdfda14.cpe.net.cable.rogers.com) joined #forth 22:27:38 --- mode: ChanServ set +o slava 23:49:57 --- join: scope (n=junk@203-97-123-216.cable.telstraclear.net) joined #forth 23:59:59 --- log: ended forth/07.02.12