The default dark-mode macOS Big Sur Alert.Button.destructive is illegible with salmon-on-gray coloring failing WCAG contrast requirements with a 1.7 score.
The Text view passed into it does not accept styling. Anyone have an idea to fix this or should an app's alert system stick to AppKit?
Related
I have just upgraded from React navigation 5 to 6 and looked at the doc for transparent modals. Unfortunately, I cannot get the previous screen to show under the modal. Instead, I get a gray background.
I have made a snack with my code to showcase my result: https://snack.expo.dev/#divone/transparent-modal-not-working
What am I doing wrong? I seem to have all the elements listed in the doc for it to work.
I am on the managed workflow of expo SDK 43.
This works for me. I had a lot of trouble specifying the background colour without it ignoring transparency and completely covering the background in a solid colour. It seems like you need to specify this information for a group, rather than for the specific screen.
You were also assigning properties which the typescript compiler did not think were valid for React Navigation 6. Check that your text editor is showing the compiler errors as you type.
<Stack.Group
screenOptions={{
presentation: "transparentModal",
contentStyle: { backgroundColor: "#40404040" },
}}
>
<Stack.Screen key="ModalScreen" name="ModalScreen" component={ModalScreen} />
</Stack.Group>
I don't know how to accurately phrase this, but after upgrading to Big Sur and XCode 12.2, I have discovered that I cannot Command-Click on a SwiftUI keyword (i.e., HStack or TextField) and get the object-specific inspector to come up. On my right panel I only ever see the inspector/settings for the .swift source file I have open; how do I get the object-specific context menu to come back?
Another issue, probably related to the first: when pressing the "+" button to insert a new object from the library, there are no longer any SwiftUI library objects available to pick; see the screenshot below:
[
The Canvas Editor must be open, and then everything works.
not sure when storyboard convert views like this. I re-installed xcode. but no luck. Xcode version is 8.3.2 (8E2002). How do I get previous view.
thanks
Open storyboard and then go to Editor -> Canvas -> Show Bounds Rectangle and uncheck it.
It looks like the storyboard content is not getting properly rendered. You can try opening a smaller storyboard and see if the content is rendering properly to know whether it is specific to this larger storyboard.
If a smaller storyboard works, try to isolate the issue in your larger storyboard by temporarily removing scenes and reopening the storyboard. Sometimes these rendering issues can be caused by a particular scene configuration.
The report a bug banner button at the top-right may provide some logs giving clues to the issue. Feel free to send those to the Apple Bug Reporter
To enable horizontal scrollbars in a table I need to style the containing DIV with "overflow: auto", highlighted in blue.
I tried it with FireBug and got the desired result. Just can't figure out out how to put the setting into APEX.
Using the theme "Blue Responsive".
I've played with this a bit in Apex 4.2.2, it should work the same in 4.2.1 I think. That particular div doesn't come from any template but you can target it with some CSS.
In the page properties, for CSS Inline, I entered the following and it seemed to work:
#report_2583625959157728_catch {overflow:auto}
(I think I've transcribed the correct id from your screenshot - you may need to check)
Unfortunately this means you'd have to do this for each report in your application individually where you want the scrollbar to appear.
Note: I haven't tested this in IE, however - last time I was mucking around with scrolling areas I found it incredibly frustrating to get it working in IE without breaking other functionality in the region - especially for Interactive reports.
You can add to Region Header:
<div style="overflow:auto;">
and to Region Footer
</div>
You can also add your css line to a report region template, if you want the scrollbar to be added to each report.
Other wise you're better of putting the overflow on a class and add it to your application's stylesheet, eg:
.myClass {overflow:auto}
you get more flexibilty to style your region this way. You can add the class to your report by setting the region attributes to class="myClass".
Note that instead of "auto", you can also try to use the element option "scroll", check the w3schools docs: http://www.w3schools.com/cssref/pr_pos_overflow.asp
I just upgraded from version 4.1 from a month or so back and suddenly my section (horozintal-nav) is being hidden on screen sizes above 768px. Prior to the upgrade it would display as a horizontal nav above 768px and as an accordion on smaller screens.
I am using compass and sass.
I have also tried cutting and pasting their example code from their documentation into the top of my page and I get the same behaviour with that as well.
The CSS that hides the control...
/* line 49, ../../../../../lib/gems/1.9.1/gems/zurb-foundation-4.3.1/scss/foundation/components/_section.scss */
[data-section='horizontal-nav']:not([data-section-resized]):not([data-section-small-style]), .section-container.horizontal-nav:not([data-section-resized]):not([data-section-small-style]) {
visibility: hidden;
}
Is anyone else having this problem?
Seems I just needed to add data-section-resized attribute to my container.
<div data-section="horizontal-nav" data-section-resized>...</div>
So simple fix, but that isn't in the zurb documentation - does anyone one know what that attribute is for?
I ran into this problem as well. The above answer didn't quite work for me because all my tabs were squashed to the top right, overlapping each other.
This thread helped me sort it out:
https://github.com/zurb/foundation/issues/3555
This isn't broken. Sizing can't be calculated correctly when elements aren't visible. If you're going to hide them and then show, you'll need to call reflow or fire the resize event to get things to calculate the correct sizes.
At least for my case, my items were being loaded AFTER Foundation was able to calculate the widths, so it always went to 0.
Hope this helps!