IE float bug

A container div that is 500px wide. Two "column" div 250px
wide. Float the left column (float left), and put a left margin on
the right column of 250. If you look at this in Firefox (pc or mac)
or Safari, it all looks good, two columns inside a container. If
you look at it in IE, it doesn't work. Does anyone know a fix for
this? Or, if I'm doing something wrong, any ideas what I'm doing
wrong. I'll attach code.
Any help would be much appreciated.
(I accidentally posted this in the dynamic HTML forum, so I
apologize for the double posting.)
BTW, there is a similar issue which display: inline will fix,
I left that in there to show that it doesn't help on this
particular problem.

See if the following is what you want. I used ids instead of
classes
though.
Oh yes, if you decide to give any padding, borders or margins
to any of the
divs, you will need to reconsider your width values, so that
you don't
encounter float drop.
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0
Transitional//EN"
http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="
http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=UTF-8" />
<title>Untitled Document</title>
<style type="text/css">

</style>
</head>
<body>
<div id="container">
<div id="left"></div>
<div id="right"></div>
</div>
</body>
</html>
PS - You may find this article useful also, because once you
start floating
divs, you will have to use clearer divs.......
http://www.complexspiral.com/publications/containing-floats/
http://www.positioniseverything.net/easyclearing.html
Nadia
Adobe® Community Expert : Dreamweaver
CSS Templates |Tutorials |SEO Articles
http://www.DreamweaverResources.com
Customisation Service Available:
http://www.csstemplates.com.au
CSS Tutorials for Dreamweaver
http://www.adobe.com/devnet/dreamweaver/css.html
"-pk-" <[email protected]> wrote in message
news:[email protected]...
>A container div that is 500px wide. Two "column" div
250px wide. Float the
>left
> column (float left), and put a left margin on the right
column of 250. If
> you
> look at this in Firefox (pc or mac) or Safari, it all
looks good, two
> columns
> inside a container. If you look at it in IE, it doesn't
work. Does anyone
> know
> a fix for this? Or, if I'm doing something wrong, any
ideas what I'm doing
> wrong. I'll attach code.
>
> Any help would be much appreciated.
>
> (I accidentally posted this in the dynamic HTML forum,
so I apologize for
> the
> double posting.)
>
> BTW, there is a similar issue which display: inline will
fix, I left that
> in
> there to show that it doesn't help on this particular
problem.
>
>
>
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0
Transitional//EN"
> "
http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
> <html xmlns="
http://www.w3.org/1999/xhtml">
> <head>
> <meta http-equiv="Content-Type" content="text/html;
charset=UTF-8" />
> <title>Untitled Document</title>
> <link href="main.css" rel="stylesheet"
type="text/css" />
> </head>
>
> <body>
> <div class="container">
> <div class="left"></div>
> <div class="right">
> </div>
> </div>
> </body>
> </html>
>
> 
> .left {
> background-color: #003399;
> height: 250px;
> width: 250px;
> float: left;
> display: inline;
> }
> .container {
> background-color: #CCCCCC;
> height: 500px;
> width: 500px;
> margin-right: auto;
> margin-left: auto;
> }
> .right {
> background-color: #999933;
> height: 250px;
> width: 250px;
> margin-left: 250px;
>
>
> }
>

Similar Messages

Float bug in Firefox 2?

Hi all, I guess I'm having a senior moment... I've coded and
re-coded over and over, but nothing seems to help. Why is my menu
(all except the first one) out of alignment in Firefox 2?
http://www.cssdreams.com/sites/optusout/

Thanks Joe. You guys are awesome. The only fix I can see for
that spacing is:
#mainmenu li {
display: inline; float:left; margin-right:-3px;
I'm usually better than this, but is not a template I built
from scratch, it was purchased...
Michael Fesser wrote:
>There's another problem with the server configuration. It
prevents the
loading of images if the HTTP referrer is empty. Since not
all browsers
send a referrer and some firewalls might filter it out for
security
reasons, so for many people the sites on that server will
look rather
strange.
No, it actually prevents my images from loading on ANOTHER
web site. My .htaccess file has a setting which prevents direct
linking of images, and it doesn't allow "certain bots" to even see
images. You can open the page just fine if it is the first web site
you visit. Here's the code in my .htaccess file.
SetEnvIfNoCase User-Agent "^WebStripper" bad_bot
SetEnvIfNoCase User-Agent "^WebWhacker" bad_bot
SetEnvIfNoCase User-Agent "^WebZIP" bad_bot
SetEnvIfNoCase User-Agent "^Wget" bad_bot
SetEnvIfNoCase User-Agent "^JOC" bad_bot
SetEnvIfNoCase Referer "cssdreams.com" local_ref=1
DirectoryIndex index.php index.html index.htm
<FilesMatch ".(gif|jpg|zip)">
Order Allow,Deny
Allow from env=local_ref
deny from env=bad_bot
</FilesMatch>

Float layout causing problems in internet explorer 5, 5.5 and 6

Hi everyone,
I have a 3-column floated fixed width layout. The right
column contains a form in the lower section. The columns are all
okay in most browsers but when I test in internet explorer 5, 5.5
and 6, the right column drops below the layout. When I tried to
troubleshoot, I found that if I took the form out of the right
column altogether then the right column would sit where it's
suppose to.
I don't know whether it's a float bug that's causing the
problem in these versions of IE or something else. Could someone
take a look and see what might be happening?
The address is:
http://www.officelinkonline.com.au/test/
http://www.officelinkonline.com.au/test/css/main.css
http://www.officelinkonline.com.au/test/css/win_ie.css
Thanks for any help offered.

I would strongly advice you to completely uninstall JSE/JDK 5.0 UPDATE 6
from you system and install JSE/JDK 5.0 UPDATE 5 or earlier (which you know works with your system)!! There is a major problem with this UPDATE 6 which just came out!! I believe it might be a security related issue! But there is definely a conflict going on with IE 6.0 SP1 and Firefox 1.5!! This update doesn't like something in our operating system!! we have the latest security updates on our computer!!
Abit Motherboard AS8 with audio card and network card enabled. Windows 2k sp4 with rollup update 1 v.2 and a hardware firewall installed!!
Our audio card screams when you go to some sites that have audiostreaming plugin on there site which uses javascript to play!! I AM NOW USING JSE 5.0 UPDATE 5 and it works great!!
IE crashes and Mozilla Firefox 1.5 crashes!! I told Sun Systems about Update 6 and haven't gotten a reply from them yet!!

Weekly build notes listings

Since there are major changes going on in the TLF weekly builds, and the ASDocs aren't up to date, and the changes made are not searchable, I thought people might want the list dumped on here so changes to particular classes would show up in a forum search. To see the changes made in Build 360, check out the TLF Blog post on it ( http://blogs.adobe.com/tlf/2009/02/tlf_api_changes_in_build_370_1.html ).
Here's the list. Maybe this could become a common practice.
Build 432, Fri May 15 2009
Changes in build 437 (2009/05/22)
    * remove flashx.textLayout.edit.UndoManager and flashx.textLayout.IUndoManager
    * Fix 2330964 BackgroundColor Placed incorrectly from TextLineFactory. Actually was in 436.
    * Fix 2326588 TextContainerManager Does Not Support Background Color
    * Fix 2330946 Remove TextContainerManager.trunctationOptions property
    * Fix 2337918 Please expose the scrollToPosition() API in TextContainerManager
    * Fix 2336672 Preserve selection when switching editingMode in TextContainerManager
    * Setting editingMode to the current editingMode should do nothing in TextContainerManager
Changes in build 436 (2009/05/22)
    * Fix 2331711 TextContainerManager now sends a DamageEvent from setText().
    * Fix 2326543 bug where selection wasn't being extended on mouse drag.
    * add [RichTextContent] metadata to SpanElement and FlowGroupElement mxmlChildren properties
    * Fix 2337740 Flex bug SDK-20964 TCM rcycling bug
    * Partial fix 2330964 background color placed incorrectly from TextLineFactory
    * Remove vestigal experiment with Tables code
    * Fix 2321538. On the Mac, the keyboard shortcuts for cmd-A,C,V,X were not working.
    * Fix 2326543, "drag select of scrolling flows doesn't expand selection".
    * Fix 2329527. Content bounds being reported was slightly different between the factory and TextFlow composer.
    * Fix 2328695 TextContainerManager Stops Receiving FocusIn Events. This is a complete fix - previously this bug was worked around
    * Added TextLineFactoryBase.isTruncated
    * Fix 2315119 - Graphic will be redrawn when link applied.
Changes in build 434 (2009/05/22)
    * Fix 2323921: RichText truncation doesn't work in all cases
Build 432, Fri May 15 2009
Changes in build 432 (2009/05/14)
    * Fixed regression that broke truncation feature
    * Added TextLineFactoryBase.isTruncated
    * Changed text line factory behavior such that scrolling is turned off when truncation options are set
Build 427, Fri May 8 2009
Changes in build 427 (2009/05/07)
    * Fix bug - RTE in computeSelectinIndexInContainer
    * Namespace change -- mxml namespace for TLF was "library:adobe/flashx/textLayout". Now it is: library://ns.adobe.com/flashx/textLayout".
    * Fix bug - Scrolled TextContainerManager Can be Difficult To Create Point Selection
Changes in build 426 (2009/05/06)
    * Fix bug - TextFlow double-deletes text when pressing the backspace or delete key
Build 422, Fri May 1 2009
Changes in build 422 (2009/04/30)
    * API Changes: TextContainerManager now has a getContentBounds function, in place of individual getters for contentLeft, contentTop, etc. ContainerController also now has a getContentBounds function, in place of individual getters. Added functions to TextContainerManager to support custom classes for ISelectionManager and IEditManager (see createSelectionManager and createEditManager).
    * API changes for TextContainerManager:
          o getInteractionManager renamed to beginInteraction(), and added a new function endInteraction() which clients should use after beginInteraction() to signal that they are done with selecting/editing. This tells the TextContainerManager that it can go back to factory mode, which is more efficient.
          o invalidateInteractionManager() removed and replaced with two new functions, invalidateSelectionFormats() which clients should called when SelectionFormats have changed, and invalidateUndoManager which clients should call to change the undo manager.
    * API Changes for InputManager
          o InputManager renamed as TextContainerManager
          o IInputManagerClient removed, now you can subclass InputManager and override its methods
    * API Changes:
          o InputManager
                + damaged property renamed to isDamaged() function
                + focusSelectionFormat renamed to focusedSelectionFormat
                + container retyped to Sprite
                + compositionWidth and compositionHeight removed as constructor parameters, now you need to set the properties on the InputManager you create
          o ContainerController
                + container retyped to Sprite
          o ISelectionManager
                + focusSelectionFormat renamed to focusedSelectionFormat
          o IConfiguration & Configuration
                + focusSelectionFormat renamed to focusedSelectionFormat
    * API Changes:
          o ISelectionManager
                + setSelection deselects if negative numbers are passed in.
                + selectAll removed, you can call ISelection.setSelection() to get the same behavior, if you need to redraw the selection, call ISelectionManager.textFlow.flowComposer.updateAllControllers().
                + flushPendingEvents moved to IInteractionHandler
                + notifyInsertOrDelete moved to IInteractionHandler
          o IUndoManager
                + clear renamed to clearAll().
                + undoLastOperation renamed to undo()
                + redoLastOperation renamed to redo()
    * API Change: SelectionEvent now contains a SelectionState, not an ElementRange; this is much cheaper for us to provide. ElementRange is now tlf_internal. ElementRange.firstLeafPosition renamed to absoluteStart, ElementRange.lastLeafPosition renamed to absoluteEnd.
    * API Change: TextScrap.copyTextScrap renamed to clone.
    * API Changes to InputManager. defaultInputManagerConfiguration renamed to defaultConfiguration. composeToController renamed to compose(), and updateToController renamed to updateContainer().
    * API Changes:
          o ISelectionManager:
                + Event handling functions moved out of ISelectionManager into new interface, IInteractionHandler
                + selectionFormat renamed to currentSelectionFormat
                + selectionState renamed to function getSelectionState()
                + setSelection now takes default parameters to select the entire flow
                + noFocusSelectionFormat renamed to unfocusedSelectionFormat
          o SelectionFormat:
                + blockAlpha reanmed to rangeAlpha
                + blockBlendMode renamed to rangeBlendMode
                + blockColor renamed to rangeColor
          o IEditManager:
                + added get undoManager()
                + added changeElementID()
                + added changeElementStyleName()
          o SelectionManager:
                + activeMark and anchorMark are now private
                + selectionChanged is private
                + setSelectionState is tlf_internal
          o EditManager:
                + stage is private
                + ChangeElementIdOperation renamed to ChangeElementIDOperation
Changes in build 420 (2009/04/28)
    * API change: Removed the misleadingly named and superfluous TextFlowLine.textIndent. Documented and ensured consistent use of TextFlowLine.lineOffset as lhe line's offset in pixels from the appropriate container inset (as dictated by paragraph direction and container block progression), prior to alignment of lines in the paragraph.
    * API change: more changes to the factory classes. ITextLineCreator is now a property of the base class, so instead of passing it in the constructor you construct and then set the property in the factory. bounds property renamed to compositionBounds, and measuredBounds renamed to contentBounds. containerController property is now private.
    * API Change: moved ITextLineCreator interface from the elements package to the compose package.
    * PlainTextExporter is now public and has methods for controlling the paragraphSeparator and whether discretionary hyphens are included in the export. To use it, you can either construct it directly, or via the TextFilter class. Removed the newlineIndicator string from IConfiguration.
    * Fixed a bug where tabs in RTL text were being being offset by textIndent and marginRight values.
Changes in build 419 (2009/04/24)
    * Once a mouseWheel event has been handled, mark with preventDefault so client applications don't also try to handle it.
    * Don't start compose if text is already composed. Optimization for callers of composeToPosition.
    * Always call resetContentTopLeft, to give more accurate top left positions, particularly for cases where the text is outdented and left aligned.
    * API CHANGE: TextLineFactory revised. It is now split into 3 classes, TextLineFactoryBase, StringTextLineFactory, and TextFlowTextLineFactory. Use StringTextLineFactory for creating TextLines from a String. Use TextFlowTextLineFactory for creating TextLines from a TextFlow. Static methods have been removed, so create a new factory in order to create lines. One factory may be reused many times, just resetting the values (text, bounds, truncation options, etc.) in between. See StaticHelloWorld.as for a simple example of how this works for Strings, see StaticTextFlow.as for a simple example of it with TextFlows.
Build 418, Fri Apr 24 2009
Changes in build 418 (2009/04/23)
    * API CHANGE: TextLineFactory revised. It is now split into 3 classes, TextLineFactoryBase, StringTextLineFactory, and TextFlowTextLineFactory. Use StringTextLineFactory for creating TextLines from a String. Use TextFlowTextLineFactory for creating TextLines from a TextFlow. Static methods have been removed, so create a new factory in order to create lines. One factory may be reused many times, just resetting the values (text, bounds, truncation options, etc.) in between. See StaticHelloWorld.as for a simple example of how this works for Strings, see StaticTextFlow.as for a simple example of it with TextFlows.
Changes in build 417 (2009/04/22)
    * Fixed Vertical Justification behavior; it now increases the spacing between consecutive lines proportionally rather than spacing lines uniformly.
    * API Changes: Renamed DisplayObjectContainerController to ContainerController, and removed IContainerController and IInternalContainerController. Wherever you used to use "IContainerController" or "DisplayObjectContainerController" now just use "ContainerController".
          o Moved some functions that were public into the tlf_internal namespace: effectivePaddingLeft, effectivePaddingTop, effectivePaddingRight, and effectivePaddingBottom.
          o ColumnState.createColumnState removed. A ColumnState constructor now takes all the relevant values, so whereever you used to do this:
                + var columnState:ColumnState = ColumnState.createColumnState(...your values here...);
          o you can now do this:
                + var columnState:ColumnState = new ColumnState();
          o ColumnState.getColumnAtIndex(index) has been renamed to getColumnAt(index). So, once you have the columnState, you do, for instance:
                + var columnRect:Rectangle = getColumnAt(0);
    * Fixed bug where spaces at end of a line would "overflow" into neighboring columns. New code keeps drawing of cursor at the column boundary and limits block selection drawing to the same bounds.
    * Enhancement to cursor navigation for Right to Left text systems. Previous code moved cursor according to logical order vs. visual order. Result was that a right arrow key press in Arabic, Hebrew or other RTL languages meant that the cursor actually moved left. New code moves cursor according to the visual order of the text based on the direction of the entire text flow. Note that changing the direction on a paragraph will not alter the behavior of the cursor, nor will the presence of LTR text within a RTL text flow. This means that if a TextFlow is set to Right to Left and a given paragraph is entirely in English and the paragraph is set to be Left to Right, the cursor will seem to move in the wrong direction. TLF does not support customization of cursor movement based on the locale or direction of anything except the parent TextFlow.
    * Fixed a bug that caused undoing an ApplyFormatToElementOperation to have no effect.
    * API Changes:
          o DisplayObjectContainer event handling functions renamed:
                + processMouseOverEvent -> mouseOverHandler
                + processMouseOutEvent -> mouseOutHandler
                + processMouseWheelEvent -> mouseWheelHandler
                + processMouseDownEvent -> mouseDownHandler
                + processMouseUpEvent -> mouseUpHandler
                + processMouseMoveEvent -> mouseMoveHandler
                + processMouseDoubleClickEvent -> mouseDoubleClickHandler
                + processFocusInEvent -> focusInHandler
                + processFocusOutEvent -> focusOutHandler
                + processActivateEvent -> activateHandler
                + processDeactivateEvent -> deactivateHandler
                + processKeyDownEvent -> keyDownHandler
                + processKeyUpEvent -> keyUpHandler
                + processTextInputEvent -> textInputHandler
                + processContextMenuSelectHandler -> menuSelectHandler
                + eventHandler -> editHandler
          o ISelectManager & SelectionManager & EditManager renamings:
                + eventHandler -> editHandler
    * API Changes: renamed IContainerController.scrollLines to getScrollDelta, renamed InputManager.scrollLines to getScrollDelta, and removed constants for default container width and height.
Changes in build 412 (2009/04/10)
    * API CHANGE: DisplayObjectContainerController methods processCopyEvent, processCutEvent, processPasteEvent, processSelectAllEvent collapsed into a single processEvent that handles all these basic events. Added to ISelectionManager a new function, processEvent for handling these same events in the SelectionManager, and removed processSelectAll, which is no longer used. cutTextScrap and pasteTextScrap moved from ISelectionManager to IEditManager, since these are editing operations.
Build 411, Fri Apr 10 2009
Changes in build 411 (2009/04/09)
    * Fixed a bug where noFocus selection format was not being set on re-activation
    * API CHANGES. These functions in IFlowComposer were renamed:
          o updateContainer -> updateToController
          o updateAllContainers -> updateControllers
          o composeContainer -> composeToController
          o composePosition -> composeToPosition
    * API CHANGE: Changing name of TextFlow.hostTextLayoutFormat to hostFormat
Changes in build 410 (2009/04/08)
    * Fix bug where leading info used for composing the next line was being saved prematurely, causing incorrect layout if the current line needed to be composed in multiple passes.
Build 409, Tue Apr 7 2009
Changes in build 409 (2009/04/07)
    * Fix bug where clicking on container when height or width NaN doesn't work. When measuring, transparent hit detect region wasn't being redrawn to correct size after composition.
    * API CHANGE: Plain-text import/export changes. Newline indicators exported based on setting in IConfiguration.newLineIndicator. On import, LF/CR/CR+LF are all recognized as new line indicators.
    * Compose to container size with scrolling on -- previously was composing to double composer size. This may flush out some invalid line bugs.
    * Fixed a bug with blockProgression="rl" and compositionWidth=NaN, lines were getting improperly clipped out so that no text appeared.
    * API CHANGE: Renaming functions in IFormatResolver. invalidateAllTargets is now invalidateAll, and invalidateTarget is now invalidate. resolveTextLayoutFormat is now resolveFormat.
    * API CHANGE: eventMirror on FlowLeafElement and SubParagraphGroupElement is now tlf_internal.
    * API CHANGE: Moving TextRange from the edit package to the elements package.
Changes in build 406 (2009/04/02)
    * API CHANGE: Renaming DamageEvent.damageStart to damageAbsoluteStart.
    * API Change: IConfiguration.includePartialLine renamed to overflowPolicy. Defined new class OverflowPolicy that describes the different policies that can be used to control whether lines that fall at the end of the container are included in the container, or not.
Changes in build 405 (2009/04/01)
    * API CHANGE: IFlowComposer.firstDamagePosition renamed to damageStartPosition.
    * API CHANGE: Rename GeometryUtil.getRangeBounds to GeometryUtil.getHighlightBounds.
    * API CHANGE: ParagraphElement.getText now takes an additional optional parameter that specifies the terminator for the paragraph. By default, this is the Unicode paragraph terminator character (\u2029), but you can make it whatever you want, including a simple newline by passing a String for the paragraphTerminator. This change is backwards compatible for current callers of getText().
    * Fix clipping problem when text is placed above the container (6 lines aligned verticalAlign = bottom in a space that fits 4 lines).
Changes in build 404 (2009/03/31)
    * Updating typgraphic case --Markup and API Change-- Now uses a new class TLFTypographicCase, and has different options. Support for "title" and "caps" dropped. Use TLFTypographicCase with TLF in preference to flash.text.engine.TypographicCase. "smallCaps" renamed to "capsToSmallCaps". "capsAndSmallCaps" renamed to "lowercaseToSmallCaps". Also made AUTO the default setting for kerning, which matches FXG spec.
Changes in build 403 (2009/03/30)
    * format Markup Changes:
          o <TextLayoutFormat> now <format>
          o When referring to a format id, don't use brackets. So this:
            <TextLayoutFormat id="english" locale="en" fontFamily="Minion Pro"/>
            <p marginBottom="15" ><span format="{english}">This text is supposed to be in Minion Pro via a named character attribute</span></p>
            Is now this:
            <format id="english" locale="en" fontFamily="Minion Pro"/>
            <p marginBottom="15" ><span format="english">This text is supposed to be in Minion Pro via a named character attribute</span></p>
    * API Changes:
          o Rename FlowElement.textLayoutFormat -> format
          o Rename FlowElement.computedTextLayoutFormat -> computedFormat
          o Rename IContainerController.textLayoutFormat -> format
          o Rename IContainerController.textLayoutFormat -> computedFormat
          o Rename DisplayObjectContainerController.textLayoutFormat -> format
          o Rename DisplayObjectContainerController.textLayoutFormat -> computedFormat
Changes in build 402 (2009/03/27)
    * verticalAlign of "middle" or "bottom" will now align to the compositionHeight (or compositionWidth in vertical text) even if the height of the text exceeds the compositionHeight. This means that lines that don't fit may be get pushed above the box, or (for middle) pushed both above and below. It also means that all lines will forced to compose to the end, so it will be quite slow to use verticalAlign in large text flows. Made some corresponding fixes to scrolling to make it work with text off the start of the container. Added some new test cases to exercise this functionality in all the different alignment settings.
    * Scrolling fixes for next/previous line with arrow keys. Fix a bug where the arrow key would move to the end of the line if the line required composition (e.g., the line was not previously in view). Also fixed a bug when scrolling up by a line where it would scroll down instead.
    * doOperation used to return an SelectionState, but with the exception of two places that were using it internally, all external callers only checked to see if it was null or not. null was being used to indicate failure, or nothing changed, which means that the operation is not placed on the undo stack. Now it returns a Boolean, true for success, false for failure. There may be further changes in this area to make FlowOperations simpler.
Changes in build 397 (2009/03/20)
    * Made DisplayObjectContainerController's and FlowElement's TextLayoutFormat properties read/write (used to be write-only).
    * Merge ContainerControllerBase class into DisplayObjectContainerController.
    * Mark TextFlow class as final
Changes in build 396 (2009/03/19)
    * Fix RTE in StandardFlowComposer.releaseLines
    * Fix possible source of the RTE on null reference from findFirstAndLastVisibleLines in ContainerControllerBase.
Changes in build 394 (2009/03/17)
    * Fix issue with changes made in StatusChangeEvent to embedded graphics by blocking recursive composition. Bug 2298043
    * Add IFlowComposer.composeInProcess property.
    * Fixed problem where first part of a link could not be replaced by a new link. New code allows partial replacement of a link element with a selection which starts at the first character.
    * Fixed a problem where the cursor was getting set to the I-beam, and wouldn't set back.
Changes in build 393 (2009/03/16)
    * Fix a bug where keyboard navigation with linked containers was causing a scroll because it was trying to scroll to a position not in the container.
Changes in build 392 (2009/03/13)
    * Removed optimization that was preventing scrolling in the logical width direction if scrolling in the logical vertical direction was turned off.
    * Removed the container-level mouseMove and rollOver handlers which were changing the link state. These are now part of the LinkElement, and added only when they are needed.
Changes in build 390 (2009/03/11)
    * Fix for application of attributes to a point selection where only the last attribute would be applied. New code applies all attributes applied to the point.
    * IContainerController.contentWidth (or contentHeight in vertical text) is now based on the actual text width, not the unjustified text width. This fixes some problems where scrolling wasn't working correctly because the reported width of the text was greater than the compositionWidth, but lines were wrapped. It does mean that to get the unjustified width you will have to set the textAlign to something other than "justify", recompose, and then get the resulting width.
    * Fix for unintended scroll when at the end of a TextFlow.
    * Fix for RTE when dragging over text generated from a factory, or non-TLF TextLines.
    * Changes for alignment and measurement. You can now set NaN for compositionWidth or compositionHeight, and TLF will compose and use the generated contentWidth or contentHeight for alignment, scrolling, etc. The composer now generates a topLeft for the bounds, so you can make a full "content bounds" using contentLeft, contentTop, contentWidth, and contentHeight.Note that this is logical bounds and not inked bounds, so there are some circumstances where ink will not fit in the content bounds.Fixed bugs in how the factory was doing vertical alignment that caused it to be a few pixels off.Fixed some incosistencies between how the standard flow composer worked and how the factory's simple composer works -- composition results should now be more uniform. Added a new test program, MeasurementGrid, for testing all this. It's still a work in progress.
Changes in build 388 (2009/03/09)
    * Fixed issue where applying link or TCY to the last span of a paragraph caused a dangling span to remain with the para terminator.
    * Fixed issue where text would go into a link when it was the last element in a paragraph. Newly typed text now goes into a new span when the selection marker is at the last index.
Changes in build 386 (2009/03/06)
    * Fixed issue with placement of underline and strikethrough on inline images.
    * Fixed placement of underline and strikethrough on text which has a baseline shift applied to it.
Changes in build 385 (2009/03/04)
    * Combined SWC 'textLayout.swc' now included in the libs directory of the build. This includes everything from textLayout_core, textLayout_edit, and textLayout_conversion.
    * Combined RSLs now included in the rsl directory of the build. Both an unsigned SWF and signed SWZ are created. These include everything from textLayout_core, textLayout_edit, and textLayout_conversion.
Changes in build 382 (2009/03/02)
    * Fix issue with composing a TextFlow containing just an empty ParagraphElement.
    * TextLineFactory will generate lines that included InlineGraphics whose source is a "class" - normally an embedded graphic.
    * Expose eventMirrors - use FlowElement.getEventMirror function to access the eventMirror.
Changes in build 381 (2009/02/27)
    * Fixed issue with graphic assigned to ILG getting the wrong sizing.
    * Factory instance functions renamed to textLinesFromString and textLinesFromTextFlow. Static functions renamin unchanged.
Changes in build 380 (2009/02/26)
    * Made backgroundColor work with TextLineFactory. This required an API change - the callback to the factory now must take a DisplayObject as its parameter, since it won't always be passed TextLines. Also, the background shapes themselves no longer include leading, so they do not exactly coincide with the selection bounds. This was another change to support calculating the shapes during composition as opposed to afterward. Also added a snapshot test as part of FactoryImportTest that uses backgroundColor, in addition to updating the existing unit tests.
Changes in build 379 (2009/02/25)
    * Fixed for multiple containers ( we were getting incorrect textLength in the containers), as well as a fix that forces scrollToPosition to compose if the text isn't composed yet.
    * Fix so that we scroll to the active position of the selection after we extend the selection with a keyboard event. Also fixed some of the TextRangeUtil functions used for nextLine, etc. to make sure text is composed through selection before processing that depends on composition results.
    * Plain text import now consistently converts \r to space; previously it was converting only the first one. Still not clear what correct behavior should be.
Changes in build 377 (2009/02/23)
    * Fix bug with importing trailing empty div elements.
Changes in build 374 (2009/02/18)
    * Added support for TextField-style leading. A new leading model value allows lineHeight to be interpreted as the distance of line's ascent from the previous line's descent. Further, lineHeight can be negative. which specifies the criteria for truncation, the string used to indicate truncation and the format for this string.
Changes in build 372 (2009/02/16)
    * Added "enableAccessibility" property to IConfiguration, defaults to false. Allows clients to avoid paying price for TextAccImpl objects unless needed.
    * Added support for truncation for text composed using TextLineFactory. The TextLineFactory methods now take a truncation options parameter, which specifies the criteria for truncation, the string used to indicate truncation and the format for this string.
Changes in build 371 (2009/02/13)
    * Fixed a number of bugs relating to scrolling by line.
    * Measurement changes. Changed the way contentHeight and contentWidth are calculated, now they reflect the size of the text, regardless of alignment. Eliminated unjustifiedContentHeight and unjustifiedContentWidth; use contentHeight and contentWidth instead.
    * Fix RTE in damage when we try to damage back one line, for textFlow that doesn't have any leaf nodes.
    * Changed InlineGraphicElement so that GraphicElements (and the TextBlocks they are part of) don't get released. Fixes RTE on null pointer in places where we access the GraphicElement.
    * Fix bug deleting all of the last Span of a paragraph, plus some of the following paragraph.
Changes in build 370 (2009/02/12)
    * Removed textFlow property from CompositionCompletionEvent. Use event.target to get to the TextFlow.
Changes in build 369 (2009/02/11)
    * Fix issues in usage of hostTextLayoutFormat
    * Fix FXG export to not export styles with value "inherit"
    * lineBreak property no longer inherits by default
Changes in build 368 (2009/02/10)
    * Fix for RTE that happens after cancelling an operation (calling preventDefault on a FlowOperationEvent).
Changes in build 367 (2009/02/09)
    * ported to Flex 4.0.0.4836. All SWCs now build with this SDK.
Changes in build 366 (2009/02/06)
    * FlowGroupElement addChild, addChildAt and replaceChildren methods now automatically delete new elements from any existing parents. Previously the code would test for parent on new elements and throw.
    * mxmlChildren FlowElement property which is normally used for mxml compilation of TextFlow objects now always deletes existing children
    * Fix a memory leak issue with the TextLayoutFormat cache
    * Fix cascade bug with non-inheriting attributes getting inherited
Changes in build 365 (2009/02/05)
    * Changed TextLayoutFormat.backgroundColor to allow setting value of "transparent" (now the default). Because of this new value for backgroundColor, backgroundAlpha now defaults to 1.
Changes in build 364 (2009/02/04)
    * Performance improvement for handling of TextFlow.hostTextLayoutFormat. The code now assumes that once set by the client the supplied object won't be changed. This avoids a copy.
Changes in build 363 (2009/02/03)
    * Performance work. Remove getCanonical from TextLayoutFormat.
    * Fix for RTE cancelling SplitParagraphOperation.
    * Fixing some float bugs.

Try searching discussions--see: http://discussions.apple.com/thread.jspa?threadID=684662
only caveat is link is dated-I googled for newer...
MacBook Pro 17" Mac mini (Intel) Mac OS X (10.4.8)

How to link a specific panel with spry multiple element sliding

How to everybody to the forum, I've searched into this forum but maybe this mine is a particular case...
I've a html page with 4 different spry multiple sliding panels, named "primo" "secondo" terzo" "quarto", and all worked fine :-)
When you go to this page the first you can see is "primo" (default).
But the problem/question is this: If i want to send an email link to my page and want to see the "terzo" panel. how???
I've try to search many examples but none one of them meet me.
This is an example of this page called test.html
Many thanks to all wants help me
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
<title>Spry Multiple Elements Sliding Sample</title>
<link href="http://labs.adobe.com/technologies/spry/css/samples.css" rel="stylesheet" type="text/css" />
<script src="http://labs.adobe.com/technologies/spry/includes/SpryEffects.js" type="text/javascript" ></script>
<script src="http://labs.adobe.com/technologies/spry/includes/SpryURLUtils.js" type="text/javascript" ></script>
<style type="text/css">
.demoDiv{
height: 150px;
overflow: hidden;
.hiddenElement{
display:none;
/* Fix IE floating bug */
position: absolute;
top: 180px;
</style>
<script type="text/javascript">
var observer = {};
observer.nextEffect = false;
observer.onPostEffect = function(e){
if (this.nextEffect)
var eff = this.nextEffect;
setTimeout(function(){eff.start();}, 10);
this.nextEffect = false;
function pannelli(currentPanel)
    // The list of all the panels that need sliding
var panels = ['slide1', 'slide2', 'slide3', 'slide4'];
var opened = -1;
// Let's check if we have an effect for each of these sliding panels
if (typeof effects == 'undefined')
effects = {};
for (var i=0; i < panels.length; i++)
if (typeof effects[panels[i]] == 'undefined'){
effects[panels[i]] = new Spry.Effect.Blind(panels[i], {from: '0%', to: '100%', toggle: true});
effects[panels[i]].addObserver(observer);
if (effects[panels[i]].direction == Spry.forwards && currentPanel != panels[i])
opened = i;
//prevent too fast clicks on the buttons
if (effects[panels[i]].direction == Spry.backwards && effects[panels[i]].isRunning)
observer.nextEffect = effects[currentPanel];
return;
if (opened != -1)
observer.nextEffect = effects[currentPanel];
effects[panels[opened]].start();
else if (effects[currentPanel].direction != Spry.forwards)
effects[currentPanel].start();
</script>
</head>
<body onload="pannelli('slide1');">
<h3>Spry Multiple elements sliding</h3>
<a href="#" onclick="pannelli('slide1');" value="Slide 1">SLIDE 1</a>
<a href="#" onclick="pannelli('slide2');" value="Slide 2">SLIDE 2</a>
<a href="#" onclick="pannelli('slide3');" value="Slide 3">SLIDE 3</a>
<a href="#" onclick="pannelli('slide4');" value="Slide 4">SLIDE 4</a>
<br />
<div id="slide1" class="hiddenElement">
<div class="demoDiv" style="background-color: yellow;">
<h4>Primo</h4>
Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed
diam nonumy eirmod tempor invidunt ut labore et dolore magna
aliquyam erat, sed diam voluptua. At vero eos et accusam et
justo duo dolores et ea rebum. Stet clita kasd gubergren, no
sea takimata sanctus est Lorem ipsum dolor sit amet.
</div>
</div>
<div id="slide2" class="hiddenElement">
<div class="demoDiv" style="background-color: pink;">
<h4>Secondo</h4>
Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed
diam nonumy eirmod tempor invidunt ut labore et dolore magna
aliquyam erat, sed diam voluptua. At vero eos et accusam et
justo duo dolores et ea rebum. Stet clita kasd gubergren, no
sea takimata sanctus est Lorem ipsum dolor sit amet.
</div>
</div>
<div id="slide3" class="hiddenElement">
<div class="demoDiv" style="background-color: magenta;">
<h4>Terzo</h4>
Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed
diam nonumy eirmod tempor invidunt ut labore et dolore magna
aliquyam erat, sed diam voluptua. At vero eos et accusam et
justo duo dolores et ea rebum. Stet clita kasd gubergren, no
sea takimata sanctus est Lorem ipsum dolor sit amet.
</div>
</div>
<div id="slide4" class="hiddenElement">
<div class="demoDiv" style="background-color: green;">
<h4>Quarto</h4>
Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed
diam nonumy eirmod tempor invidunt ut labore et dolore magna
aliquyam erat, sed diam voluptua. At vero eos et accusam et
justo duo dolores et ea rebum. Stet clita kasd gubergren, no
sea takimata sanctus est Lorem ipsum dolor sit amet.
</div>
</div>
<br />
Test per collegamenti esterni<br /><br />
<a href="test.html?">vai al pannello I°</a> |
<a href="#">vai al pannello II°</a> |
<a href="#">vai al pannello III°</a> |
<a href="#">vai al pannello IV°</a>
</body>
</html>

silemma wrote:
else if (effects[currentPanel].direction != Spry.forwards)
effects[currentPanel].start();
</script>
</head>
<body onload="pannelli('slide1');">
Change the above to
else if (effects[currentPanel].direction != Spry.forwards)
effects[currentPanel].start();
var params = Spry.Utils.getLocationParamsAsObject(); //get the URL parameter
if (params.slide) { // if the slide parameter exists
    var slide = 'slide'+params.slide; // slide = slide+slide parameter
} else { // otherwise
    slide = 'slide1'
</script>
</head>
<body onload="pannelli(slide);"> 
Then when calling the page use the following notation: http://localhost/test/test.html?slide=3 where ?slide=3 is the third slide
I hope this helps.
Ben

Text in column 2 starts under the lowest line of column 1?

Hello,
i posted this question also in the Dutch forum, but there are not so many viewers in there, and now i found this forum.
I have a problem with Dreamweaver CS4 (i am still very new with DW, but manage to create something)
I am working with CS4 and have created a page.
this page contains 5 regions:
4 on top of each other, of which the 3rd contains 2 colums.
I have uploaded this page and on my pc (IE7) it looks good, the text in the right column appears at the start of this region, at the same hight as the start of the buttons in the left column.
[img]http://img8.imageshack.us/img8/2412/42056350.jpg[/img]
If i view this page on the laptop (IE6), than there is a difference. The text in the right column starts at the bottom of the lowest button in the left column.
[img]http://img8.imageshack.us/img8/5560/laptopq.jpg[/img]
Does anybody know why or how to prevent this?
I hope you can help. (i will give it a try in changing some settings, but i don't really know what to look for), so thanks in advance!
Fred & Suze

DWFAQ.info wrote:
Won't this put rightcol under leftcol on the left side?
I think it's the IE 3px text jog bug or the IE float bug.
Ditch the marquee tag it's non-standard HTML markup.
It is deprecated by the W3C and not advised by them for use in any HTML documents for a reason.
I think your marquee is rendering as one line of text and is giving you a 3px jog.
Yes it most likely is the 3px jog.
My advice is if youre designing a 'static' site (as this is) it is best to use floats instead of margins to position containers.
Floating the left and right column will work just fine and provide a more stable contruction.
To test if it is the 3px jog take 3px away from the width of the right column.
If you dont want to float google '3px jog' for a solution, there are several.

Simple CSS Layout Test - Gap in IE

Hey Gang,
I'm takig the first steps away from Table based layouts into
CSS Fluid
layouts.
I put together a quick and simple layout.
There is a 2-3 pixel gap between the Left Column and Main
Content Column in
IE 6 and 7 (It's fine in Firefox).
Would someone mind taking a peek and suggesting what I may be
missing or
could do better?
Thanks
-Dave
<style type="text/css">

</style>
<div id="Container">
<div id="header">Header</div>
<div id="Leftnav">Left</div>
<div id="content">content</div>
<div id="footer">Footer</div>
</div>

I've been following the other thread IE Float bug as well.
I think the challenge that comes up with using the -3 on the
floated div's
right margin, is you will then get overlap/underlap in
Firefox and other
non-IE browsers.
In my code example below, the word "Content" in that div tag
will now
over/underlap into the red sidebar div(with a -3 on the
sidbar div)
This would normally have been a great time to use the old IE
* hack, but IE7
defeats that now.
It's almost that we'd need to use a style for IE (with -3),
and a different
style for everything else.
Does the @Import trick still work with IE7?
If not, then it's down to javascript browser detection, and I
guess changing
the ID of the Div tag to call either a normal style or an IE
friendly style.
If this is all true, what a p.i.t.a :>
"BW" <[email protected]> wrote in message
news:[email protected]...
> I'm a newbie so don't take my word as Gospel, but I
believe it is due to
> the IE bug and floats. IE adds 3px to the right of a div
that is floated
> left.
>
> Do a search for 3px jog. One search results suggests
adding
> margin-right: -3px; to your left div.
>
> This seems to work, but I do not know what that does to
other browsers.
>
> One of the guru's on here will give you the correct
reasons and answers
>
> BW
>
> "Dave Bar" <[email protected]> wrote in message
> news:[email protected]...
>> Hey Gang,
>>
>> I'm takig the first steps away from Table based
layouts into CSS Fluid
>> layouts.
>>
>> I put together a quick and simple layout.
>> There is a 2-3 pixel gap between the Left Column and
Main Content Column
>> in IE 6 and 7 (It's fine in Firefox).
>>
>> Would someone mind taking a peek and suggesting what
I may be missing or
>> could do better?
>> Thanks
>> -Dave
>>
>> <style type="text/css">
>> 
>> </style>
>>
>> <div id="Container">
>> <div id="header">Header</div>
>> <div id="Leftnav">Left</div>
>> <div id="content">content</div>
>> <div id="footer">Footer</div>
>> </div>
>>
>
>

Text in Arabic - Periods at "start" of phrase (right justified) instead of at the end (left)

Hey guys, so I'm using CC and I'm trying to copy text from a word document written in arabic. I havethe preferences set to Indic and it is written correctly (from right to left). The only problem is the periods are showing up at the beginning of the sentences instead of the end. Any thoughts?

DWFAQ.info wrote:
Won't this put rightcol under leftcol on the left side?
I think it's the IE 3px text jog bug or the IE float bug.
Ditch the marquee tag it's non-standard HTML markup.
It is deprecated by the W3C and not advised by them for use in any HTML documents for a reason.
I think your marquee is rendering as one line of text and is giving you a 3px jog.
Yes it most likely is the 3px jog.
My advice is if youre designing a 'static' site (as this is) it is best to use floats instead of margins to position containers.
Floating the left and right column will work just fine and provide a more stable contruction.
To test if it is the 3px jog take 3px away from the width of the right column.
If you dont want to float google '3px jog' for a solution, there are several.

Problem inserting images Dreamweaver CS3

Hi, I have Dreamweaver CS3 and Dreamweaver MX 2004 loaded on
the same machine, iMac G5. My OS is 10.4.10 Tiger and all updates
are current. No particular reason, just never got around to
uninstalling the latter. Here's the problem in CS3, but not MX
2004. I can't insert images into my HTML page by any of the
following methods: insert menu at the top of the screen, or click
and drag the file. Copy and pasting the code from another page
won't even work. The only way it works is by typing in the raw code
into code view. I get a strange warning when I try to copy and
paste: something like Java script error. I thoroughly checked my
mark-up and there's no a single speck of Java Script anywhere. I've
also get other strange warnings while trying to put in images:
floating bugs.html, margin bugs.html, and others (sorry this is not
verbatum, but you get the idea). I've tried shutting dowm the
computer and rebooting, but that didn't help either. When I
switching over to MX 2004, same files, I was able to insert images
in all of the various ways mentioned above. So I'm thinking, maybe
I should uninstall Dreamweaver CS3, and reinstall from disk. So, I
did the uninstall, and emptied my trash, but haven't reinstalled
yet. Thought that I should run this by the forum first. thanks for
any help. Yesterday I got multiple sudden unexpected "quits" while
using both versions, losing unsaved work. thanks for any
suggestions, Deborah North

Troubleshooting JavaScript errors in Dreamweaver
http://www.adobe.com/cfusion/knowledgebase/index.cfm?id=tn_19105#dat
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
==================
"dnorth" <[email protected]> wrote in
message
news:feinqm$173$[email protected]..
> Hi, I have Dreamweaver CS3 and Dreamweaver MX 2004
loaded on the same
> machine,
> iMac G5. My OS is 10.4.10 Tiger and all updates are
current. No particular
> reason, just never got around to uninstalling the
latter. Here's the
> problem in
> CS3, but not MX 2004. I can't insert images into my HTML
page by any of
> the
> following methods: insert menu at the top of the screen,
or click and drag
> the
> file. Copy and pasting the code from another page won't
even work. The
> only way
> it works is by typing in the raw code into code view. I
get a strange
> warning
> when I try to copy and paste: something like Java script
error. I
> thoroughly
> checked my mark-up and there's no a single speck of Java
Script anywhere.
> I've
> also get other strange warnings while trying to put in
images: floating
> bugs.html, margin bugs.html, and others (sorry this is
not verbatum, but
> you
> get the idea). I've tried shutting dowm the computer and
rebooting, but
> that
> didn't help either. When I switching over to MX 2004,
same files, I was
> able to
> insert images in all of the various ways mentioned
above. So I'm thinking,
> maybe I should uninstall Dreamweaver CS3, and reinstall
from disk. So, I
> did
> the uninstall, and emptied my trash, but haven't
reinstalled yet. Thought
> that
> I should run this by the forum first. thanks for any
help. Yesterday I got
> multiple sudden unexpected "quits" while using both
versions, losing
> unsaved
> work. thanks for any suggestions, Deborah North
>

OnMouseOut to Multi_Slides demo

I've searched the forum and found similar questions, but I can't seem to make it work.
I'm using the Spry setup from the multi_slides demo. Initially the links were set to 'onclick'. I have changed this to 'onmouseover' and it seems to work fine.
http://labs.adobe.com/technologies/spry/samples/effects/multiple_slides_sample.html
My next task is to add 'onmouseout' to retract the slide, as it is when the page first opens. (But, I don't actually want to reload the page)
I assume that this can be done, as the page opens with all slides closed/retracted.
I can fake it by adding 'slide0' to the 'onmouseout', but this slide doesn't exist and it seems wrong.
Any ideas on how to do this correctly?
...After more testing, the dummy panel 'panel0' does work, but it's buggy. Sometimes a panel will stick in the open position, then reverse the out and over functions. And sometimes a panel will stick open, and other panels will open on top of it.
It seems that the 'onmouseout' function doesn't have the same usability defense thingys that the 'onclick/onmouseover' function has.
So, maybe that is the question... Ahhh, I don't know. Any thoughts would be appreciated.
<style type="text/css">
        .msDiv{
            overflow: hidden;
            border-bottom: #720050 2px solid ;
        .hiddenElement{
            display:none;
            /* Fix IE floating bug */
            position: absolute;
            top: 260px; /* Make this whatever is needed from the browser top */
    </style>
    <script type="text/javascript">
var observer = {};
observer.nextEffect = false;
observer.onPostEffect = function(e){
    if (this.nextEffect)
        var eff = this.nextEffect;
        setTimeout(function(){eff.start();}, 10);
    this.nextEffect = false;
function myPanelsSlides(currentPanel)
    // The list of all the panels that need sliding
    var panels = ['slide1', 'slide2', 'slide3', 'slide4', 'slide5', 'slide6', 'slide7'];
    var opened = -1;
    // Let's check if we have an effect for each of these sliding panels
    if (typeof effects == 'undefined')
        effects = {};
    for (var i=0; i < panels.length; i++)
        if (typeof effects[panels[i]] == 'undefined'){
            effects[panels[i]] = new Spry.Effect.Slide(panels[i], {from: '0%', to: '100%', toggle: true});
            effects[panels[i]].addObserver(observer);
        if (effects[panels[i]].direction == Spry.forwards && currentPanel != panels[i])
            opened = i;
        //prevent too fast clicks on the buttons
        if (effects[panels[i]].direction == Spry.backwards && effects[panels[i]].isRunning)
            observer.nextEffect = effects[currentPanel];
            return;
    if (opened != -1)
        observer.nextEffect = effects[currentPanel];
        effects[panels[opened]].start();
    else if (effects[currentPanel].direction != Spry.forwards)
        effects[currentPanel].start();
    </script>
        <ul>
          <li onmouseover="myPanelsSlides('slide1');" onmouseout="myPanelsSlides('slide0');"><a href="#">Slide 1 Title</a></li>
          <li onmouseover="myPanelsSlides('slide2');" onmouseout=""><a href="#">Slide 2 Title</a></li>
        </ul>
      <div id="slidebox">
        <div id="slide1" class="hiddenElement">
          <div class="msDiv" >
            <h3>Heading</h3>
            <ul class="msDivlist">
              More stuff in the slide
            </ul>
          </div>
        </div>
        <div id="slide2" class="hiddenElement">
           <div class="msDiv" >
             <h3>Heading</h3>
            <ul class="msDivlist">
               More stuff in the slide
             </ul>
           </div>
         </div>
      </div>

In the end, to fix the bugginess, I set the panels to activate with onclick. I kept the onmouseout set to activate the invisible/dummy panel0. It works, but it seems kinda' hacky.

Double Float Margin Bug "error"

I did a browser compatibility check on one of the pages that
I am building and got this error.............
"Line 112, Double Float Margin Bug 'error'
When a margin is applied to a floated box on the same side as
the direction of the float, the margin is doubled. This bug only
affects the first float in a row of one or more floats.
Affects: Internet Explorer 6.0
Likelihood: Very Likely"
I have many thumbnails for a gallery page in their own divs,
within the content div, and they are floated in there.
When I viewed solutions, they suggested:
"When a margin is applied to a floated box on the same side
as the direction the box is floated AND the floated box is the
first one inside its containing box, the margin is doubled. (In
other words, a left-floated box with margin-left set to move it
away from its containing box will be twice as far away from the
left edge of the containing box as intended.)
SOLUTION
Specify display: inline; for the affected float.
DETAILED DESCRIPTION
This bug only reproduces when the floated element's margin
extends in the same direction as the float itself, and is between
the float and the container box's inside edge. Subsequent floats
with similar margins won't reproduce this bug- just the first float
in any row of floated elements."
Does anyone have any solutions, suggestions as how to fix
this? I will attach my code. And if anyone has a better solution as
to laying my thumbnail divs in another div container, please say
so. The reason I am putting them in separate divs is because that
is what someone suggested to use them with Lightbox2. He said they
needed some kind of special CSS to enable some of the functions and
they (the thumbnails) were easier to style if they were in their
own separate divs. I'm open for any suggestions.
Thanks!

Just add "display:inline" to the styling like this:
.image {
background-color: #121922;
height: 100px;
width: 100px;
float: left;
margin: 20px;
display: inline;
}

IOS 5 calendar bug: Floating Appointments

This is a bug with iOS 5's calendar that you can reproduce yourself. This bug was not in iOS 4:
1. Enter an appointment into iCal on your Mac running Mac OS X 10.6.8.
2. Make the appointment a FLOATING appointment, which means that its time will ALWAYS stay the same, regardless of which time zone you are in.
3. Sync your calendar using MobileMe.
4. Now go to your iPhone 4 running iOS 5.0.1.
5. Sync your calendar using MobileMe.
6. Make sure your iPhone's calendar settings have Time Zone Support turned ON.
7. Go into your calendar, and look for your floating appointment.
8. On the MONTH view, your appointment looks JUST FINE! The times are correct!! However, if you try to EDIT THE EVENT, you will see the gigantic bug crop up: the times are completely & wildly off from your original floating times. If you try to modify the times, then you will only mess up the times on the month view even more. There is no way to get the iPhone's calendar appointments to accurately reflect the floating time on both the month view and when editing the appointment. It is completely off.

Thanks for the info, I gave it a try but am still having the same problem as I mentioned before.
I believe your issue is a bit different than mine. My 3 outlook canlanders are there, two of them are displaying (my wife's calendar and my work), however the primary calendar I use in outlook isn't displaying. It shows that it is selected, however none of my events are there. I'm able to add new events in this calendar just fine, but all of my events that were there prior to the upgrade in iOS aren't.
I've already checked settingings to make sure it syncs all old data also, but it still doesn't display events from my main calendar.
So the issue isn't that I am missing all Outlook calendars, rather I am missing only one of the 3.

BUG: Large floating point numbers convert to the wrong integer

Hi,
When using the conversion "bullets" to convert SGL, DBL and EXT to integers there are some values which convert wrong. One example is the integer 9223370937343148030, which can be represented exactly as a SGL (and thus exactly as DBL and EXT as well). If you convert this to I64 you get 9223370937343148032 instead, even though the correct integer is within the range of an I64. There are many similar cases, all (I've noticed) within the large end of the ranges.
This has nothing to do with which integers can be represented exactly as a floating point value or not. This is a genuine conversion bug mind you.
Cheers,
Steen
CLA, CTA, CLED & LabVIEW Champion
Solved!
Go to Solution.

Yes, I understand the implications involved, and there definetely is a limit to how many significant digits that can be displayed in the numeric controls and constants today. I think that either this limit should be lifted or a cap should be put onto the configuration page when setting the display format.
I ran into this problem as I'm developing a new toolset that lets you convert all the numeric formats into any other numeric format, just like the current "conversion bullets". My conversion bullets have outputs for overflow and exact conversion as well, since I need that functionality myself for a Math toolset (GPMath) I'm also developing. Eventually I'll maybe include underflow as well, but for now just those two outputs are available. Example:
I do of course pay close attention to the binary representation of the numbers to calculate the Exact conversion? output correctly for each conversion variation (there are hundreds of VIs in polymorphic wrappers), but I relied in some cases on the ability of the numeric indicator to show a true number when configured appropriately - that was when I discovered this bug, which I at first mistook for a conversion error in LabVIEW.
Is there a compliancy issue with EXT?
While doing this work I've discovered that the EXT format is somewhat misleadingly labelled as "80-bit IEEE compliant" (it says so here), but that statement should be read with some suspicion IMO. The LabVIEW EXT is not simply IEEE 754-1985 compliant anyways, as that format would imply the x87 80-bit extended format. An x87 IEEE 754 extended precision float only has 63-bit fraction and a 1-bit integer part. That 1-bit integer part is implicit in single and double precision IEEE 754 numbers, but it is explicit in x87 extended precision numbers. LabVIEW EXT seems to have an implicit integer part and 64-bit fraction, thus not straight IEEE 754 compliant. Instead I'd say that the LabVIEW EXT is an IEEE 754r extended format, but still a proprietary one that should deserve a bit more detail in the available documentation. Since it's mentioned several places in the LabVIEW documentation that the EXT is platform independent, your suspicion should already be high though. It didn't take me many minutes to verify the apparent format of the EXT in any case, so no real problem here.
Is there a genuine conversion error from EXT to U64?
The integer 18446744073709549568 can be represented exactly as EXT using this binary representation (mind you that the numeric indicators won't display the value correctly, but instead show 18446744073709549600):
EXT-exponent: 0x100000000111110b
EXT-fraction: 0x1111111111111111111111111111111111111111111111111111000000000000b
--> Decimal: 18446744073709549568
The above EXT value converts exactly to U64 using the To Unsigned Quad Integer "bullet". But then let's try to flip the blue bit from 0 to 1 in the fraction part of the EXT, making this value:
EXT-exponent: 0x100000000111110b
EXT-fraction: 0x1111111111111111111111111111111111111111111111111111100000000000b
--> Decimal: 18446744073709550592
The above EXT value is still within U64 range, but the To Unsigned Quad Integer "bullet" converts it to U64_max which is 18446744073709551615. Unless I've missed something this must be a genuine conversion error from EXT to U64?
/Steen
CLA, CTA, CLED & LabVIEW Champion

Who know this bug "ERROR: floating-point constants should not appear"

anyone know how to solve this bug
ERROR: floating-point constants should not appear
Error preverifying class org.javabluetooth.stack.BluetoothStack
com.sun.kvem.ktools.ExecutionException: Preverifier returned 1

HI,
it seems that ur using the package "org.javabluetooth.stack.BluetoothStack" in WTK1.0 or 2.0 which does not support floating point. The above package uses float data type. You can download the new version of WTK (2.1) which supports floating points.

DW bug? Not clearing floats via overflow:hidden

OK so I think I found a bug in Dreamweaver CS3's Design View.
I have been using an alternative technique to clear floats using
overflow:hidden. It's not a new technique but it is very clean. You
can read about it here:
http://www.quirksmode.org/css/clearing.html
I believe the technique is valid, standards-compliant and
rendered by all modern browsers. What happens in DW is that the
floats are not cleared, and the containing box collapses. Here's
some very basic code to test it:

It's a well known flaw in CS3 and earlier Design view. It's
fixed in CS4.
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
==================
"sly one" <[email protected]> wrote in
message
news:g5ip1q$90r$[email protected]..
> OK so I think I found a bug in Dreamweaver's Design
View. I have been
> using an
> alternative technique to clear floats using
overflow:hidden. It's not a
> new
> technique but it is very clean. You can read about it
here:
>
http://www.quirksmode.org/css/clearing.html
> I believe the technique is valid, standards-compliant
and rendered by all
> modern browsers. What happens in DW is that the floats
are not cleared,
> and the
> containing box collapses. Here's some very basic code to
test it:
>
>
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0
Transitional//EN"
> "
http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
> <html xmlns="
http://www.w3.org/1999/xhtml">
> <head>
> <meta http-equiv="Content-Type" content="text/html;
charset=UTF-8" />
> <title>Clear Floats with Overflow
Hidden</title>
> <style type="text/css">
> 
> </style></head>
>
> <body>
>
> <div class="container" style="overflow: hidden;
width: 100%">
> <div class="left">
> <p>The left column.</p>
> <p>The left column.</p>
> <p>The left column.</p>
>
> <p>The left column.</p>
> </div>
> <div class="right">
> <p>The right column.</p>
> <p>The right column.</p>
> <p>The right column.</p>
> </div>
>
> </div>
>
> </body>
> </html>
>

IE float bug

Similar Messages

Maybe you are looking for