-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Subliminal incorrectly thinks elements are invisible in non-portrait orientations #135
Comments
Doubt it'd be helpful, but here's the trace file from the Instruments run https://s3.amazonaws.com/uploads.hipchat.com/1658/151914/AnCa4c6gojjpUMA/SubliminalLandscapeTrace.trace.zip |
Thanks for the terrific bug report @MaxGabriel! I can reproduce. I imagine that it’s a matter of needing to transform the context into which the view is rendered, but I'm not quite sure how to do that myself... @aegolden can you take a look? |
Hey @MaxGabriel, we're looking into the bug. In the meantime, you can fall back on UIAutomation's visibility routine using the following: #import <Subliminal/SLUIAElement+Subclassing.h>
@interface SLUIAElement (LandscapeVisibility)
- (BOOL)uiaIsVisible;
@end
@implementation SLUIAElement (LandscapeVisibility)
- (BOOL)uiaIsVisible {
return [[self waitUntilTappable:NO thenSendMessage:@"isVisible()"] boolValue];
}
@end Sorry for the inconvenience. |
Cool no problem. |
…tions. (refs #135) As a workaround for the failure of our visibility routine.
…tions. (refs #135) As a workaround for the failure of our visibility routine.
…ntations. (refs #135) As a workaround for the failure of our visibility routine.
…ntations. (refs #135) As a workaround for the failure of our visibility routine.
Hi, I think there's a bug where Subliminal incorrectly labels an element invisible in non-portrait orientations. I created a sample project replicating this bug.
I believe the problem comes from this block of code. In landscape, Subliminal considers the center to be covered, but in portrait it thinks it is not.
I tried to investigate down into
numberOfPointsFromSet:...
andrenderViewRecursively:...
, but got lost in the Core Graphics code. Any idea what the problem could be? My suspicion is that its a screen coordinates != logical coordinates type of issue, but I'm not sure.Steps to replicate
git clone https://github.com/MaxGabriel/SubliminalLandscapeBug.git
cd SubliminalLandscapeBug
git submodule update --init
open Subliminal.xcodeproj
EDIT (@wearhere): This issue originally described the failure as occurring in landscape orientations, but tests added in #180 revealed that the failure actually occurs in any non-portrait orientation. This issue's title and description have been updated accordingly.
The text was updated successfully, but these errors were encountered: