[svn] 4439: Fix FxTextArea focus issue.

Revision: 4439
Author: [email protected]
Date: 2009-01-08 06:54:17 -0800 (Thu, 08 Jan 2009)
Log Message:
Fix FxTextArea focus issue. In FxTextArea.partAdded(), if there is a scroller,set scroller.focusEnabled to false. With this change, calling focusManager.getFocus() for the embedded textView object will skip over the scroller in the chain and return the desired FxTextArea. The FxTextArea will now have the expected focus ring and you should only have to click once, not twice, in a FxTextArea to get focus.
QE Notes:
Doc Notes: None
Bugs: SDK-18101, SDK-18211
Reviewers: Gordan, Alex
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-18101
http://bugs.adobe.com/jira/browse/SDK-18211
Modified Paths:
flex/sdk/trunk/frameworks/projects/flex4/src/mx/components/FxTextArea.as

Pierre-Charles David a écrit :
> Hi,
>
> I've got a very strange issue and I don't know where to look for to fix
> it. In some Eclipse configuration I use, SWTBot does not work at all: it
> fails the very first method with a WidgetNotFoundException.
[snip]
Well, I found the issue:
SWTBot declares a dependency to org.apache.log4j but does not indicate
any specific version. However, it uses APIs which only appeared in log4j
1.2.12 (at least Logger.trace(), maybe others).
In the Eclipse installation I have which did not work ("Topcased RCP"),
there was a bundle which provided the org.apache.log4j package, but
using log4j version 1.2.8. As it happens, Eclipse decided to provide
this one to SWTBot instead of other versions available from different
bundles (1.2.12 and 1.2.15). The test failed with an internal
NoSuchMethodError, which must have been caught by some code and wrapped
as the WidgetNotFoundException I saw.
Removing the plugin with log4j 1.2.8 from the test's run configuration
solves the issue.
I have opened bug #286527 about this.

Similar Messages

[svn] 2210: Fix for layout issue of AIR apps on mac when only width or height is

Revision: 2210
Author: [email protected]
Date: 2008-06-24 11:56:52 -0700 (Tue, 24 Jun 2008)
Log Message:
Fix for layout issue of AIR apps on mac when only width or height is
set on root WindowedApplication tag.
Bugs: SDK-14643.
QA: Yes, very much so.
Reviewer: Ryan
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-14643
Modified Paths:
flex/sdk/branches/3.0.x/frameworks/projects/airframework/src/mx/core/WindowedApplication. as

Updates:
I've opened a bug with Adobe regarding this issue:
http://bugs.adobe.com/jira/browse/FP-4362
Also, the Cancel operation on a FileReference causes the same issue to happen as does loading. I really think it's an operating system focus issue.
UPDATE:
Looks like this has already been tracked and is scheduled to be fixed:
https://bugs.adobe.com/jira/browse/FP-2785

[svn] 4859: -Fix packaging timing issue that was caused by the rebuilding of the air applicationupdater .

Revision: 4859
Author: [email protected]
Date: 2009-02-05 10:15:22 -0800 (Thu, 05 Feb 2009)
Log Message:
-Fix packaging timing issue that was caused by the rebuilding of the air applicationupdater. The recompiled files would get laid down properly only to have the old files put back down on top of them. I also made sure the build directory was removed after updateAIR ran so it would not be included in the package
-removed bundles.properties from the wireframe project
bug:SDK-19128
qa:yes
doc:no
checkintests:pass
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-19128
Modified Paths:
flex/sdk/branches/i10/build.xml
flex/sdk/branches/i10/frameworks/build.xml
Removed Paths:
flex/sdk/branches/i10/frameworks/projects/wireframe/bundles.properties

Hi Chris,
I have confirmed this is an AIR SDK 13.0.0.83 bug.
I have reported this bug to Adobe Bugbase, and I also included the workaround:
https://bugbase.adobe.com/index.cfm?event=bug&id=3750892
The workaround is:
Simply comment the <externalSwfs> tag in your -app.xml will solve this bug, like this: 
DarkStone
2014-04-28

[svn] 2913: Fix SWFLoader sizing issue (SDK-16497) Refactor some classes to try to fix ASDoc build.

Revision: 2913
Author: [email protected]
Date: 2008-08-19 21:55:11 -0700 (Tue, 19 Aug 2008)
Log Message:
Fix SWFLoader sizing issue (SDK-16497) Refactor some classes to try to fix ASDoc build.
Review: DJL
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-16497
Modified Paths:
flex/sdk/branches/3.0.x/frameworks/projects/airframework/src/mx/managers/WindowedSystemMa nager.as
flex/sdk/branches/3.0.x/frameworks/projects/framework/src/mx/controls/SWFLoader.as
flex/sdk/branches/3.0.x/frameworks/projects/framework/src/mx/managers/ISystemManager.as
flex/sdk/branches/3.0.x/frameworks/projects/framework/src/mx/managers/SystemManager.as

Thanks for sharing.

Lightroom and Windows mouse focus issues.

In one aspect Lightroom have been always behaving different from other Windows application: Its speed of grabbing mouse focus and moving window to the foreground is exaggerated. This problem will be observed only by people using their WinXP computers in "X11 mode", like with Unix, what allows to perform interaction with processes associated with windows without ever clicking on, or raising such window. Should you be working on large computer clusters as I do, this focusing feature its a blessing.
This how you can reproduce: Use Tweak UI to adjust the mouse behavior. Select "Mouse," step down to "X=Mouse" and check "Activation follows mouse." Do not select "autoraise."
Now your WinXP will behave similar to the real X11 xterm with mouse having the "no raise selection" policy. Its not quite identical to xterm, but it really works perfectly in most cases.
Except... well, except with Lightroom. Lightroom grabs the pointer and pushes the window to the foreground in splits of a second. For example, go to
"Help|About Adobe Lightroom" to see the credit window. It appears than as usual, but since the help menu will be dismisses, the pointer stands on the main Lightroom window, what makes the credits window vanish in split of a second. No chance to see it!
Another case: Assume that Lightroom uses almost the entire desktop down to the task bar, and your browser window is smaller. Select the browser on the taskbar and try to move mouse to it. No chance! Lightroom will take over and pop itself to the foreground again. The only solution is to minimize Lightroom. And than sometimes something happens that Lightroom will not restore itself anymore! The "Restore" operation is grayed out, one can only Maximize it. We have reported this numerous times before.
I am aware that this problem relates only to WinXP users with X11 mouse mode, but with Lightroom reaching now a high degree of maturity, maybe we could take a look at this problem as well?

In order to overcome most of the known navigation and/or focus issues you need to be using the following:
<li>Forms 10.1.2.3 or newer (latest is 11.1.2). If/when you are using 10.1.2.3 you would also need to install patch ID 9593176 as this contains additional fixes for focus issues.
<li>JRE 1.6.0_26 or newer (latest is 1.6.0_30). The latest is always recommended as it contains the most up to date fixes for both technical issues and security issues.
Patches are only available on MyOracleSupport: http://support.oracle.com

70d focus issue - admins answers please.

Will you admit that lot of 70d suffering focus issues?
Will you fix it by firmware update? Recall?
It's a big shame that everybody on the net speak about it and waste 1000 dollars and you just ignore us!!
I would like to get some answers please.
Thank you.

I have the same issue. It's odd, I've had the 70d since November-ish. I used to be a '2nd shooter' at weddings w/ just my olf Nikon d5100 & a 50mm 1.8 for portraits, and the kit lens for wides. Total N00b. .I started getting a grasp of things, and my wedding partner decided to double-book a bunch fo weddings. Since he was a Canon user, and I was looking for an upgrade to the 5100, I switched to canon & bought a 70D. Since then he's complained about focus issues, blaming me, and since i'm newer to this gig, took it to heart and assumed it was me. I have a steady hand, and believe to not be any kind of user error - I know how to shoot.
Today I discovered the 50+ pages of forum complaints on http://photography-on-the.net/forum/showthread.php?t=1354075 & the Canon forums http://forums.usa.canon.com/t5/EOS/When-will-canon-fix-the-focus-issues-with-the-70D/td-p/79330/page... - to find out that it might have been the camera all along? I just told the guy to screw off this weekend and quit because obviously I wasn't the photographer he needed... This focus problem hasn't been confirmed for me this week, but shooting w/ Tamron 17-50 2.8 & canon f4L 24-105, sure seems like theyr'e in the range of speculation here...
Will there be an update/recall to fix this?
Today I stumbled across a video (from the canon forums link) showing two photographers describing their issue w/ live view vs viewfinder view, and focusins on the center focal point for lenses 1.4-4.0... this sounds a LOT like my issue and am praying I can find an answer to this without having to call canon and RMA it.

[svn:fx-trunk] 12814: Addressing focus issue in DataGrid introduced by a recent fix.

Revision: 12814
Revision: 12814
Author:   [email protected]
Date:     2009-12-10 15:18:25 -0800 (Thu, 10 Dec 2009)
Log Message:
Addressing focus issue in DataGrid introduced by a recent fix.
QE notes: None
Doc notes: None
Bugs: SDK-24665
Reviewer: Alex
Tests run: Checkin
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-24665
Modified Paths:
    flex/sdk/trunk/frameworks/projects/framework/src/mx/controls/DataGrid.as

Revision: 12814
Revision: 12814
Author:   [email protected]
Date:     2009-12-10 15:18:25 -0800 (Thu, 10 Dec 2009)
Log Message:
Addressing focus issue in DataGrid introduced by a recent fix.
QE notes: None
Doc notes: None
Bugs: SDK-24665
Reviewer: Alex
Tests run: Checkin
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-24665
Modified Paths:
    flex/sdk/trunk/frameworks/projects/framework/src/mx/controls/DataGrid.as

Should I spend the $280.00 to have Canon fix my 70D auto-focusing issue?

Should I spend the $280.00 to have Canon fix my 70D auto-focusing issue? Or just return back to my very much trusted Rebels?
Solved!
Go to Solution.

MelekalsCanon wrote:
Very much appreciate your taking time to send a response. As a new user I wasn't sure if anyone would bother. Allow me to add a little more to my first post. I fit in that niche between amateur and a person with clients. For over 10 years I have covered events for a non-profit agency capturing the look and feel of 20+ events per year and was given permission to purchase a few cameras over the year. My decision from the beginning was to use the Canon Rebel. Images were spot on and only once did I have an issue with one of them (after shooting outside events in 105 degree temps for 3 days).
So, when I retired a year ago it was for me a pretty simple choice to get a Canon for myself - especially since at that time the 70D was on the cover of magazines and was very highly touted. I also did a lot of desktop publishing and photo editing which helped me realize I wanted the best sensor, sharpness, resolution and lens I could afford - the 70D. My post was actually a result of reading many online responses including your very informative replies about the 70D focusing issues. My biggest concern is that I will spend several hundred dollars and maybe, just maybe get back a camera which captures better focused images, but still not as sharp as the lower end Rebels I was using. I had hoped to purchase my first "L" lens and really get excited - not repair the most expensive camera I've bought to date.
Thanks again and before it gets noted by someone...yes, I should have pushed this issue sooner and then at least the warranty would have covered the cost. An expensivve lesson learned. But I will have to add that at least one authorized Canon repair dealer told me they have had several folks feel like I did - that it was the photographer/me as a new user having the issue and not the camera. I now know it's my camera.
Let me clarify that I don't own a 70D, so anything I say about it is from watching what others have said, mainly in this forum. But it is disconcerting to see so much complaint about a camera that's supposed to have an innovative focusing system. One is strongly tempted to suspect that they went overboard in trying to make the camera serve both still photographers and videographers.
That said, I'm not a great fan of the Rebel line, because they lack autofocus microadjustment and I have at least one otherwise excellent Canon lens that would be useless without it. (The 70D does have AFMA, a point in its favor.)
As far as spending the $280 for the repair, I understand why it's a hard call. If I were in your shoes and were convinced that Canon understands the issue and would fix it correctly and permanently, I guess I'd go for it. If you don't think they do, but fell that you need something a cut above the Rebels, this may be a good time to buy a leftover or refurbished 7D. Even though I now have a 5D3, I still use my 7D's a fair amount and have been very happy with them. And the 7D2 has gotten such a favorable reception that's it's almost bound to make more 7D's available at a decent price.
Bob
Boston, Massachusetts USA

Is there a fix for 5d ii focus issue

Hello, I just purchased the 5Dii used but the owner said the camera was working perfectly. I notice that when I take photos the photos do not look sharp. I am shooting in raw and using fast enough settings that they should be sharp. I tried different lenses and a tripod still same results when viewed at 100%. So I have been reading about the 5d ii having focus issues and was wondering if there is a fix to this problem? Also, I read that with 21 mp the photos won't look sharp in the view finder or when viewed at 100% has anyone else heard this? Any suggestions would be helpful. I am thinking I need to return the item which is a shame, I was so excited to get the 5d ii and very disappointed to be having this issue.

I don't suggest using the viewfinder to judge quality of photos -- it's too small.
There are no focus "issues" with a 5D II -- it's an excellent camera. It doesn't have the advanced focus system of the 5D III but if the focus points on your 5D II tell you that something is correctly focused then it should be correctly focused.
There are NUMEROUS things that can cause problems (none of which are defects.)
1) If you allow the camera to auto-select it's focus point, remember that the camera will always pick the focus point which can lock focus at the closest focusing distance. Suppose you're taking a photo of someone's face, but on the side of the frame there's a bush -- and that push is in far enough that one of the focus points is on the bush. The camera will focus on the bush and NOT on your subject's face. Usually you will want the camera to focus on the nearest subject, but when shooting shots with distracting elements in the frame which are closer then your intended subject, you need to pick the focus point you want the camera to use rather than allow it to auto-select the point.
2) If focusing at a particularly low focal ratio (especially at close distances) the depth of field can get REALLY thin. If you want focus on your subject's eyes -- you will need to carefully position the focus point and lock focus on your subject's eyes -- otherwise you may end up getting a focus lock on their nose (as an example) and the eyes will be slightly soft.
3) In the default "one shot" mode, the camera will focus prior to taking the shot. When focus lock is achieved the camera will stop adjusting focus. If either you or your subject move after that point, the camera will NOT re-adjust -- you'll get a soft shot. With moderate f-stops usually a small movement wont change focus distance enough to matter -- this is mostly an issue at shallow f-stops. But if shooting action where you KNOW your subject is moving and focus distance is changing, you need to use the "AI Servo" mode which continuosly updates focus.
4) Your 5D II allows you to adjust the focus accuracy of a lens. Some lenses will routinely focus just slightly in front or behind your intended focus distance. When you detect that you have a lens that does this, the camera can compensate. This adjustment requires that you set up an accurate focus test to determine if an adjustment is needed and how much. Do not attempt to make an adjustment by using regular every-day shots... use a carefully controlled focus target, tripod, etc. There's a procedure for doing this.
5) If you suspect inaccuracy with focus points (and you really need to be careful to use controlled circumstances before arriving at such a conclusion) you can test by switching to "live view" mode to see if you get different results. Live view mode does not use the phase-detect auto-focus points... it uses contrast-detection focus instead. Contrast detection is slower but in theory should be able to provide more accurate focus as long as you have a subject with some decent contrast. If live view is consistently outperforming the standard phase-detect AF mode then you may need to perform focus adjustment on your camera (this is specific to each lens you own... this is because each lens can behave differently.)
Lastly... your camera records which AF points were used when it takes a photo. This data can be displayed IF you use the Canon EOS Utility (which should have come with your camera). It'll put the familiar focus array overlaying your photo and highlight the active point(s). Just be aware that if you did a "focus and recompose" that the camera is going to report which focus point was used to lock focus but wouldn't know you recomposed the shot. If you're not recomposing and your subject distance wasn't changing then the utility should be accurate.
Incidentally, Apple's "Aperture" software also allows you to view the Canon focus point data. As far as I'm aware, this is not available in Lightroom or Photoshop.
Tim Campbell
5D II, 5D III, 60Da

[svn:fx-trunk] 12994: * Fixes for two issues that were showing up in FB.

Revision: 12994
Revision: 12994
Author:   [email protected]
Date:     2009-12-16 06:44:45 -0800 (Wed, 16 Dec 2009)
Log Message:
Fixes for two issues that were showing up in FB.
QE notes:
Doc notes:
Bugs: SDK-24669, SDK-24686
Reviewer: Corey
Cycloner: George
Tests run: checkintests
Is noteworthy for integration: yes, fixes two FB issues.
Code-level description of changes:
modules/compiler/src/java/flex2/tools/PreLink.java
    Modified postRun() to swap in the root CompilationUnit's Logger
    when validating it's StyleContainer. This allows the warnings
    from StylesContainer.validate() to be persisted across incremental
    compilations. This fixes SDK-24686.
modules/compiler/src/java/flex2/compiler/Source.java
    Made getLogger() public, so it could be called from PreLink.
modules/compiler/src/java/flex2/compiler/CompilerAPI.java
    Modified compile() to check forcedToStop() after each PreLink
    batch. This fixes SDK-24669.
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-24669
    http://bugs.adobe.com/jira/browse/SDK-24686
    http://bugs.adobe.com/jira/browse/SDK-24686
    http://bugs.adobe.com/jira/browse/SDK-24669
Modified Paths:
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/CompilerAPI.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/Source.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/linker/CULinkable.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/tools/PreLink.java

[svn:fx-4.x] 14289: Fix DataGrid mirroring issues when layoutDirection="rtl " and direction="rtl":

Revision: 14289
Revision: 14289
Author:   [email protected]
Date:     2010-02-19 13:08:54 -0800 (Fri, 19 Feb 2010)
Log Message:
Fix DataGrid mirroring issues when layoutDirection="rtl" and direction="rtl":
- headers get messed up when resizing, moving or sorting a column because the transform matrix in UIFTETextField wasn?\226?\128?\153t always updated when width was changed
- when moving a column, the headerSelection sprite was moving in the wrong direction
- when dragging a row, the drag image was backwards and the x offset between the image and the mouse pointer was wrong
QE notes:
Doc notes: None
Bugs: SDK-25424, SDK-25426, SDK-25440, SDK-25442, SDK-25452, SDK-25460, SDK-25462, SDK-25464
Reviewed By: Hans
Tests run: checkintests
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-25424
    http://bugs.adobe.com/jira/browse/SDK-25426
    http://bugs.adobe.com/jira/browse/SDK-25440
    http://bugs.adobe.com/jira/browse/SDK-25442
    http://bugs.adobe.com/jira/browse/SDK-25452
    http://bugs.adobe.com/jira/browse/SDK-25460
    http://bugs.adobe.com/jira/browse/SDK-25462
    http://bugs.adobe.com/jira/browse/SDK-25464
Modified Paths:
    flex/sdk/branches/4.x/frameworks/projects/framework/src/mx/controls/DataGrid.as
    flex/sdk/branches/4.x/frameworks/projects/framework/src/mx/controls/dataGridClasses/DataG ridDragProxy.as
    flex/sdk/branches/4.x/frameworks/projects/framework/src/mx/controls/dataGridClasses/DataG ridHeader.as
    flex/sdk/branches/4.x/frameworks/projects/framework/src/mx/core/UITextField.as
    flex/sdk/branches/4.x/frameworks/projects/framework/src/mx/managers/DragManagerImpl.as
    flex/sdk/branches/4.x/frameworks/projects/spark/src/mx/core/UIFTETextField.as

Dear Pallavi,
Very useful post!
I am looking for similar accelerators for
Software Inventory Accelerator
Hardware Inventory Accelerator
Interfaces Inventory
Customization Assessment Accelerator
Sizing Tool
Which helps us to come up with the relevant Bill of Matetials for every area mentioned above, and the ones which I dont know...
Request help on such accelerators... Any clues?
Any reply, help is highly appreciated.
Regards
Manish Madhav

[svn:fx-trunk] 5367: The changes here are mostly fixing some sizing issues.

Revision: 5367
Author: [email protected]
Date: 2009-03-17 15:26:35 -0700 (Tue, 17 Mar 2009)
Log Message:
The changes here are mostly fixing some sizing issues.
For the FlashContainerPlaceholder, the first child is now MyFlexContentHolder, which extends mx.flash.FlexContentHolder but meets the invariant that it has 1 child and that child is FlexContentHolderThumbnail, which I?\226?\128?\153ve added as a swc to the project. I changed this by accident last time to refer to mx.flash.FlexContentHolder, when it should've referred to a concrete instance created by Flash from a swc. I also added a chrome of 151x151 to match the FlexContentHolderThumbnail since otherwise the container itself would have no chrome at all, and this let?\226?\128?\153s it size correctly.
Also, for sizing, in a container, rather than sizing to the size of the chrome, I now size to the size of the FlexContentHolder thumbnail that all FlexContentHolder?\226?\128?\153s have. This means in ContainerMovieClip, I don?\226?\128?\153t need to override bounds anymore.
ContainerMovieClip now implements IVisualElementContainer.
Also, I fixed a resizing event bug in UIMovieClip where the resize event was getting dispatched more than once.
QE Notes: -
Doc Notes: -
Bugs: SDK-19271, SDK-19788, SDK-19789
Reviewer: Glenn
tests: checkintests
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-19271
http://bugs.adobe.com/jira/browse/SDK-19788
http://bugs.adobe.com/jira/browse/SDK-19789
Modified Paths:
flex/sdk/trunk/frameworks/projects/flash-integration/src/mx/flash/ContainerMovieClip.as
flex/sdk/trunk/frameworks/projects/flash-integration/src/mx/flash/FlexContentHolder.as
flex/sdk/trunk/frameworks/projects/flash-integration/src/mx/flash/UIMovieClip.as
flex/sdk/trunk/frameworks/projects/utilities/build.xml
flex/sdk/trunk/frameworks/projects/utilities/src/FlashComponentPlaceholder.as
flex/sdk/trunk/frameworks/projects/utilities/src/FlashContainerPlaceholder.as
Added Paths:
flex/sdk/trunk/frameworks/projects/utilities/libs/
flex/sdk/trunk/frameworks/projects/utilities/libs/FlexContentHolderThumbnail.swc
flex/sdk/trunk/frameworks/projects/utilities/src/MyFlexContentHolder.as

Hello Everyone,
We request you all to try your applications with http://labs.adobe.com/technologies/flashplatformruntimes/air3-5/
Release Notes - http://labsdownload.adobe.com/pub/labs/flashplatformruntimes/shared/air3-5_flashplayer11-5 _releasenotes.pdf
Please let us know how it goes.
-Thanks
Pahup

[svn:osmf:] 14298: Fix some ASDoc issues.

Revision: 14298
Revision: 14298
Author:   [email protected]
Date:     2010-02-19 17:26:18 -0800 (Fri, 19 Feb 2010)
Log Message:
Fix some ASDoc issues.
Modified Paths:
    osmf/trunk/framework/OSMF/org/osmf/elements/BeaconElement.as
    osmf/trunk/framework/OSMF/org/osmf/events/MediaErrorCodes.as
    osmf/trunk/framework/OSMF/org/osmf/media/MediaPlayer.as

[svn:osmf:] 13142: Fixing embedded font issues.

Revision: 13142
Revision: 13142
Author:   [email protected]
Date:     2009-12-22 08:16:15 -0800 (Tue, 22 Dec 2009)
Log Message:
Fixing embedded font issues.
Modified Paths:
    osmf/trunk/apps/samples/framework/WebPlayer/html-template/index.template.html
    osmf/trunk/apps/samples/framework/WebPlayer/src/WebPlayer.as
    osmf/trunk/libs/ChromeLibrary/src/org/osmf/chrome/controlbar/widgets/ScrubBar.as
    osmf/trunk/libs/ChromeLibrary/src/org/osmf/chrome/controlbar/widgets/URLInput.as
    osmf/trunk/libs/ChromeLibrary/src/org/osmf/chrome/fonts/Fonts.as

I am not sure how to fix the problem using the FGL framework, but here is a way to get the right result
In the CSS file under the @media only screen and (min-width: 769px) section, modify the following style rules
#menu {
    clear: both;
    float: left;
    margin-left: 0;
    width: 20%;
    display: block;
    vertical-align:top;
#content {
    clear: none;
    float: right;
    margin-right: 0%;
    width: 80%;
    display: block;
Having said that, you will do well to scrap FGL and have a look at Bootstrap

[svn:osmf:] 10644: fixed some layout issues with the MediaPlayerWrapper.

Revision: 10644
Author:   [email protected]
Date:     2009-09-28 09:36:33 -0700 (Mon, 28 Sep 2009)
Log Message:
fixed some layout issues with the MediaPlayerWrapper.
Modified Paths:
    osmf/trunk/apps/samples/framework/MediaPlayer/src/com/adobe/strobe/players/MediaPlayerWra pper.as
    osmf/trunk/apps/samples/framework/MetadataSample/src/MetadataSample.mxml
Property Changed:
    osmf/trunk/libs/VAST/

Hi Chanh
I have not come upto the level of testing the file generated with IRS. Will keep you posted what happens there.
Shannon,
Apparently the new version of 1546868 fixes the issue for box number 7. But if the amounts are huge in box numbers 1 or 3 or 15a (they use these in my client) then the amount overflows to the nearby box. So we have again opened an issue again with SAP & will keep you posted withwhat SAP comes up with.
Thanks
Regards
Morgan

[svn] 4439: Fix FxTextArea focus issue.

Similar Messages

Maybe you are looking for