Has anyone experienced this issue on the iOS 16 beta?
The text wrapping in a simple label seems it is different in the iOS 16 beta.
As you can see in the image attached, the "essentially" text goes to the line below in the iOS 16 beta, this is just a dummy example but we have seen a lot of screens where this wrapping happens.
For the record: it is the same label with the same leading and trailing constraints values, the only thing that has changed is the IOS version.
As our app needs to be "Pixel-perfect" this is a problem because we have a lot of screens to fix and we want to avoid adding iOS version logic in the code.
Related
Scenario: iOS6 & iOS7 (4"inch) sharing the same XIB.
Problem: Both display different layout, albeit sharing the same constraints, etc.
The following images are snapshots of simulated iOS6 & iOS7 version of the SAME Layout/Constraints:
Notice the different layout patter for the fields & button:
Question: How can I get iOS6 & iOS7 layouts in sync; i.e., behave the same?
Here's a snapshot of all the constraints:
It appears that I had two conflicting vertical spaces (that wasn't flagged by Xcode 5).
Near the bottom of the complaint list (see above), there are two 'Vertical Space' constants for the 'Please wait while we...' label: (92) vs (26).
By removing one of them (26), the (iOS 6) layout has adjusted to be in sync with its iOS 7 counterpart.
Still odd...
... why didn't BOTH environments behave the same in the first place?
I was playing with adaptative CSS by changing my Google Chrome window size when I noticed that the Twitter Bootstrap page seems to "make google chrome fail" on certain occasions.
Steps to reproduce (from a desktop computer):
Start with a blank Google Chrome tab, full screen
Visit http://twitter.github.com/bootstrap/
Gradually make the window narrower, letting go the mouse every 100 pixels or so.
Keep going until you get the "totally mobile version", at around 400px (The blue "View project on github" button is on top of the white "Download Bootstrap" button, and they are both full-width).
Now make the window thick again, letting the mouse go after every 20 pixels or so.
Chances are that you will get weird behaviour while doing steps 4 or 5 - Chrome gets confused about the sizes, or forgets to draw a vertical region of the page (which is rendered white). I've also managed to get a "phantom side pane" in some rare occasions.
I've tried in two different computers, and I still get the same issues (both using Ubuntu 12)
The thing is, other responsive sites don't have this issue. See for example http://css-tricks.com/ . You can change its size all you want, and Chrome never has any trouble rendering the multiple layouts it has (in fact, it has more layouts than twitter bootstrap).
So I can only conclude that this problem is twitter-bootstrap-specific. Probably related with the way the CSS rules or HTML content is written, or maybe related with the way files are structured.
I'm using twitter bootstrap as a base for one of my sites, and I'd like to solve this issue. Does anyone have any ideas on how to proceed?
If you believe this is bootstrap-specific this should be posted to the Twitter Bootstrap Github Pages instead of SO. However, I've been participating in an issue ticket reg. this which was closed after we pointed out that we're unable to reproduce the error on both Chrome / OS X and Chrome / Win 7 with the same browser build as the OP. This suggest that this is a platform specific chrome-error rather than a problem with the Bootstrap toolkit. With that said, I'd raise a ticket with the chrome team including your build # and OS/Platform setup.
Link to the Github Issue
My application is set up to use the flex framework_3.3.0.4852.swf as an rsl, which works fine reporting no errors. However, now some of the charts have lost there legend text for both vertical and horizontal axis.
When analysing the styles/properties, the UITextField used for axis text has a text width of zero! The data is set correctly, and all parent components are set to a size that shouldn't influence the text width.
Initially I thought I had a style bleed problem, but then I discovered that if I built the application with all libraries (including the framework) merged in, the problem goes away.
I have also done some tests using inline styles to override any style bleeds that might have been coming through, this had no effect.
Has anyone seen this type of thing before relating to using rsl's?
UPDATE:
I have since found some known bugs in the adobe support knowledge base https://bugs.adobe.com/jira/secure/IssueNavigator.jspa?
Here are the 2 bugs that relate to my question:
1) https://bugs.adobe.com/jira/browse/FLEXDMV-1883
This is reported as fixed, however the next bug seems to disagree, I'm going to investigate further into this and update this question again.
2) https://bugs.adobe.com/jira/browse/FLEXDMV-2065
UPDATE:
Ok I removed the embedded font being used for charts from my stylesheets, from both module and application. The UITextField text has now appeared again. So clearly an embedded font issue.
So in summary, if you have a modular application, you need to embed fonts in both module and application for them to be picked up correctly. But if you use the framework swf as an rsl, you cant use an embedded font with chart axis text.
UPDATE:
Now I have a real problem, 2 of my charts use a rotation effect. When the effect plays and finishes, the axis text disappears because I need to use an embedded font when applying effects to text in this way. But of course I cant use an embedded font for chart styles when I have the framework swf as an rsl!! Not sure how to get around this one?
After some attempts to override the way Axis labels are rendered for chart components when using SDK 3.x, and not getting very far. I have decided that the short term resolution is unfortunately to roll back our builds, not using the framework swf as an RSL until we can upgrade to version 4.x of the SDK.
The main reasons for this are:
1) If the framework swf is an RSL in your project, you cant use an embedded font for chart axis labels, as they don't show up. If you analyse their properties, you'll find all data is correct except text width will be set to zero.
https://bugs.adobe.com/jira/browse/FLEXDMV-1883 - modular app related similar bug
https://bugs.adobe.com/jira/browse/FLEXDMV-2015 - RSL related
https://bugs.adobe.com/jira/browse/FLEXDMV-2065 - RSL related
2) If embedded fonts are removed from charting component Axis styles to fix the above issue, you then cant apply effects to the same components. This is because you need to use an embedded font to apply effects correctly to the Axis labels.
The only way to fix this issue is to upgrade SDK to 4.x as the chart Axis uses Label instead of UITextField.
My Xcode has suddenly began to display unreadable text in the source editor. No other apps are affected. It is most notable with white/bright-colored text on a black background but it occurs in every theme.
The text looks like the the background is bleeding through the foreground text characters. It doesn't really look like "the jaggies" that you used to see with bitmapped fonts.
Here is s side by side comparison between Xcode and the terminal using the same orange on black theme, at the same font of Menlo 12. Even in the reduced resolution screen shot, the difference is obvious. On screen, the terminal text display is crisp and easily readable while the Xcode text is barely readable and, as a practical matter, useless.
I don't know when the problem may have started because I haven't been working in Xcode recently. The only change is that I added a second monitor to my dev box but removing the monitor did not resolve the problem.
I tried using the com.apple.dt.Xcode defaults to set the anti-aliasing of Xcode to 24 point but that too had no effect.
I'm stumped. My next step will be to reinstall Xcode but I was hoping someone else may have hit this problem before and has a neater resolution.
A reinstall of Xcode resolved the issue. Haven't the foggiest why.
Update:
This answer over at Ask Different might be relevant as well.
I was reviewing the CSS docs for version 4.6 and saw this in the doc:
"In BlackBerry Device Software version 4.6, the BlackBerry Browser provides full support for CSS 2.1, excluding pseudo-elements and dynamic pseudo-classes, system fonts, and generated content."
I am running the 4.6.0.190 emulator for the bold and I cannot get any padding to work. My other CSS is working fine, such as font family and font size but that is about it. Anything related to the box model (margins, padding) and positioning does not work and according to the docs, it should.
Any suggestions?
One thing I've noticed doing development on the BlackBerry emulator is that it is very inaccurate in a lot of situations compared to the actual device.
Unfortunately I don't have a list of what things work or don't work the same as the physical device on the emulator, however I've noticed several small discrepancies that make it (in my opinion) almost useless to rely upon for development.
Many of these discrepancies are box model related. For example, the padding on the real BlackBerry Bold behaves properly, while the emulator gives more padding than it should, causing things to render wrong.
Box model related things do work on the emulators I've tried, however I've had some problems, especially related to widths of elements, however not the same issues you've described.
My recommendation is to get your hands on a BlackBerry Bold to really see what everything looks like.