I have one of those popular ghost buttons with a transparent background and a 3px yellow border. On the hover, focus and active state the background is filled with yellow.
Has experienced that when you click a button and the use the back button in Safari the state of the button seems to be set to active or focus, which means in my case that it has the yellow background even though it is supposed to be transparent when I come back to the first page.
I tried with Safari and iOS 8 on a iPhone 4S.
Related
Have a funny issue going on and no idea where to start. I have an iOS app that's built with Nativescript & Vue and while in dark mode the button colors in dialogs are off. Sometimes they are a bright blue (which is normal and what I want), but most of the time they are a darker color blue which are really hard to see. Randomly the correct color will show, but mostly the incorrect darker and I can't seem to pattern it out - just random.
The dialog is a confirm dialog that is being called in the typical Nativescript Vue manner - nothing custom being called.
Any direction or idea why this may be happening is greatly appreciated.
Incorrect button color
Correct button color
Note: Dialog message is purposely blacked out
Try writing Button styles at the end of your application level style sheet.
Button {
color: blue; // any color your like
}
Unfortunately you can not have separate styles for light / dark mode yet. There is an open issue you might want to follow.
Try to use custom model component for alert dialog or https://market.nativescript.org/plugins/nativescript-fancyalert alert dialog.
Say you've got a Xcode app with embedded web view exposing a simple HTML5 page.
This page has a title and an input tag and a nav top bar (position: fixed; top:0;).
When the user tap in it the first time, the whole screen scrolls up to enable the keyboard appears while maintaining the input tag visible, when I tap the enter button.
The issue I face is that my HTML is not restored identically (I mean, it scrolls down back, but my top bar is shifted about 10 pixels below the top edge of the screen.
But when I tap the keyboard hide button, the scrolls restore my initial view, with no issue.
Anyone experienced the issue before? Any clue of what going on or a way to work around this?
Ps: issue is present on iOS 7 (7.1.2). I didn't tested on iOS 8 as my app must support iOS 7.
I finally ended up with adding an explicit keyboard withdrawing by applying blur() the the input as follows:
<input ng-change="$(this).blur()">
This immediately makes the keyboard disappearing, while the hw initial scrolling is reversed.
Iam having code in which clicking on button pops up dialogue, and clicking on that goes to another dialog, the background of first dialog has been transparent where as the background of next dialog has been black, is it possible to resize the black background of second dialog, please help me thanks
I'm working on an app which has buttons at the bottom of the screen(looks like tab bar). I found that if I enable the access to control center in app, there will be a notable delay between tapping on the buttons and the highlighted image showing. In fact the highlighted image will never show if I do not hold on the touch for at least about 0.5 second. I'm wondering if there is a way to disable the delay even the access of control center in app is ON so that users of my app will know the buttons did have been tapped. Any hint will be appreciated.
I have a jQuery Mobile radio button set that when viewed on a desktop browser displays a gray-filled dot for inactive selections and a red-filled dot with a white center for the active selection.
However, when I view the page in a mobile device (either iOS or Android), I get nothing for the inactive selections and a curious new graphic for the active selection. The new graphic is a red dot but has three white bars stacked vertically upon one another and to the right side of the dot.
Normally I wouldn't really care but this graphic looks like it could be a corporate logo or something and therefore is somewhat distracting. Plus the missing gray dots for inactive selections is annoying. Anyone know what is happening here?