Recommended Posts

I'm not sure if this will help or not, but this is the code I use to make "about:blank" transparent

#browser,
#content > tabbox > tabpanels {
  background-color: transparent !important;
}

#main-window[stylish-url="about:blank"] #content browser { 
   opacity: 0 !important;
}

Hi foxxyn8

I couldnt get this to work , i have a white background instead....does this works on windows 7 only cos i am using vista64 =p

Hi foxxyn8

I couldnt get this to work , i have a white background instead....does this works on windows 7 only cos i am using vista64 =p

that's the old code. use this instead (requires stylish):

#appcontent,
#content > tabbox > tabpanels {
  background-color: transparent !important;
}

#main-window[stylish-url="about:blank"]:not([onclose^="PrintUtils"]) #content browser { 
   opacity: 0 !important;
}

Does using stylish and having userchrome.css have any differences (startup UI responsiveness, blah blah)? I'm already satisfied with my userchrome so I'm thinking about removing stylish.

Foxxyn8 had pointed out that userChrome.css can't handle anonymous content, if I understood correctly.

The other advantages of using Stylish may be useful to beginners (moi) like previews (which have a "proof-reading" ability) and not having to restart the browser to see the effect of changes.

Foxxyn8 had pointed out that userChrome.css can't handle anonymous content, if I understood correctly.

The other advantages of using Stylish may be useful to beginners (moi) like previews (which have a "proof-reading" ability) and not having to restart the browser to see the effect of changes.

To expand on this, the difference is that userContent/Chrome are user stylesheets whereas stylish uses user agent(UA) stylesheets. The difference being, in particular, UA can apply styles to native anonymous elements and to CSS anonymous boxes.

Also stylish handles the functions of both userChrome and userContent.

As far as performance goes, I've never noticed any difference. Stylish just makes it easier all around.

Back to beg for more help. :laugh: . What do I add to grey out the favicons on the bookmark toolbar, or everywhere else for that matter? I saw some code that did it earlier in the thread, but I haven't been able to find it again.

https://www.neowin.net/forum/topic/921416-share-your-custom-firefoxminefield-4-stylish-scripts/page__view__findpost__p__593741318

I don't like "text-shadow" (or "etched" effect or anything that makes letters less clear-cut) which I see in a lot of drop-down menus and dialog boxes/panels. Is there a general way to fix that?

In userStyle.css, this works great:

* { text-shadow: none !important; }

I don't like "text-shadow" (or "etched" effect or anything that makes letters less clear-cut) which I see in a lot of drop-down menus and dialog boxes/panels. Is there a general way to fix that?

In userStyle.css, this works great:

* { text-shadow: none !important; }

I don't think it gets any more general than that. You're telling every selector not to use a text-shadow.

I don't think it gets any more general than that. You're telling every selector not to use a text-shadow.

Foxxyn8, but how do I get it to work for the UI (chrome?) of the browser (as opposed to the page content)?

I already have this as a specific example:

#FindToolbar *{ -moz-appearance: none !important; background: #333 !important; color:black !important; font-weight: bold !important; text-shadow: none !important;}

Without it, certain text (Next, Previous) in the Find Toolbar would appear "different" (blurry to me) when there is no search text entered.

So what I want to know is whether there's a universal code that can be used in my style that affects various aspects of the UI (chrome?).

(Just to be clear, I have separate styles in Stylish to reflect chrome versus content.)

I don't think it gets any more general than that. You're telling every selector not to use a text-shadow.

Interesting (and a bit alarming at first). I put the same line in my "chrome" Stylish code. And now I don't see the text-shadow effect :) . The alarming bit is that I don't see the text at all in some cases unless I hover over where it should be. This is okay sometimes but could cause panic at other times.

Interesting (and a bit alarming at first). I put the same line in my "chrome" Stylish code. And now I don't see the text-shadow effect :) . The alarming bit is that I don't see the text at all in some cases unless I hover over where it should be. This is okay sometimes but could cause panic at other times.

That's probably because the color property of the selector is the same as the background-color property. For instance if the text color is black, the background-color is black, a white text shadow makes the text visible. If you remove that text shadow the text becomes unreadable.

That's probably because the color property of the selector is the same as the background-color property. For instance if the text color is black, the background-color is black, a white text shadow makes the text visible. If you remove that text shadow the text becomes unreadable.

That is fair enough. But just out of interest, how is "inactive" text selectively shadowed? Like the example I gave for the Find Toolbar. Or another example when one views a drop-down menu such as "Edit". If no content has been copied by Ctrl+C, the Paste options are shadowed. I'm asking because I'm not sure of how to get the info with the Domain Inspector.

that's the old code. use this instead (requires stylish):

#appcontent,
#content > tabbox > tabpanels {
  background-color: transparent !important;
}

#main-window[stylish-url="about:blank"]:not([onclose^="PrintUtils"]) #content browser { 
   opacity: 0 !important;
}

Awesome!! Thnx for the pointers!

That is fair enough. But just out of interest, how is "inactive" text selectively shadowed? Like the example I gave for the Find Toolbar. Or another example when one views a drop-down menu such as "Edit". If no content has been copied by Ctrl+C, the Paste options are shadowed. I'm asking because I'm not sure of how to get the info with the Domain Inspector.

They're using the [disabled = "true"] attribute. In the right panel of DOM Inspector choose Object - DOM Node. That will show you all the attributes of the chosen selector.

post-350326-0-18854500-1302271474.png

They're using the [disabled = "true"] attribute. In the right panel of DOM Inspector choose Object - DOM Node. That will show you all the attributes of the chosen selector.

...

Thanks for the pointer :)

So now I have:

* {text-shadow: none !important}
* [disabled="true"] {color:#555!important; font-weight: bold!important}

Looks like it's going to take me a lot more time before I can learn to use DOM Inspector for less obvious things :(

Anyone can help me out with these 2 problems ?

I have a weird line and i need to get rid of it

How to change the text color of on the "NEXT" button in the FIND BAR?

Re. the second one, this works for me:

#FindToolbar .findbar-find-next {color: green!important;}

Anyone can help me out with these 2 problems ?

I have a weird line and i need to get rid of it

How to change the text color of on the "NEXT" button in the FIND BAR?

#FindToolbar .findbar-find-next:not([disabled]) {
        color: red !important;
}

#navigator-toolbox::after {
	height: 0px !important; 
}

Thanks for the pointer :)

So now I have:

* {text-shadow: none !important}
* [disabled="true"] {color:#555!important; font-weight: bold!important}

Looks like it's going to take me a lot more time before I can learn to use DOM Inspector for less obvious things :(

* [disabled="true"] 

works, but you should use

*[disabled = "true"]

Re. the second one, this works for me:

#FindToolbar .findbar-find-next {color: green!important;}

#FindToolbar .findbar-find-next:not([disabled]) {
        color: red !important;
}

#navigator-toolbox::after {
	height: 0px !important; 
}

thank you both for the help ^^!

i also managed to figured out the text color for findbar "NEXT", "PREVIOUS" and "HIGHLIGHT" button !! :laugh:

#FindToolbar toolbarbutton:not([disabled]) {
    color: #fff !important;
}

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • If its the devs fault you would think Unreal would help M$ take full advantage of Unreal and work with them to fix the performance issues. Otherwise they are catching unwarranted bad press.
    • Thanks for the advice guys, I'll give my current GPU a clean and then run the benchmarks to see how similar it is. Hopefully a bit of a clean-out will help it last a bit longer.
    • Pretty sure those will still be in this game. The series' well-explored psychosis themes will return as well.
    • "performance issues? what performance issues?!"
    • Microsoft making much needed change to Windows 11, 10 Patch Tuesday security updates by Sayan Sen Recently, Microsoft delivered its latest Defender patches for Windows 11 ISOs. These definitions are released from time to time alongside the general security updates available during Patch Tuesday. Speaking of Defender, the company has now announced another important change that affects how security updates are delivered to enterprise devices running Windows. According to a recent announcement, Microsoft Defender for Endpoint's endpoint detection and response (EDR) updates will no longer be bundled with the monthly Windows security updates or Patch Tuesdays. Instead the company is shifting delivery of these updates to Microsoft Update, bringing EDR servicing in line with several other Microsoft Defender components. If you recall, Microsoft last year moved PowerShell updates to Microsoft Update (MU) as well since it provides automatic updates for Microsoft products and services. Thus the move is intended to allow Microsoft to deliver EDR improvements and security enhancements independently of the OS's regular monthly update cycle; this should enable faster deployment of protection updates without requiring organizations to wait for the next Patch release. For those unfamiliar, Microsoft Defender for Endpoint's EDR capabilities are designed to help organizations detect, investigate, and respond to advanced threats across managed devices. Keeping these components updated is critical for maintaining protection against evolving attack techniques. The rollout has already began for Windows 10 devices in late May 2026 (last month) and Microsoft says it will gradually expand support to Windows 11 and the remaining supported Windows versions over the coming months. The company expects deployment across Windows 10 and Windows 11 to be completed by fall 2026 or around Q3 of this year. Once the transition is complete, EDR updates will be delivered through Microsoft Update using KB5005292, provided the required prerequisite updates have already been installed. Microsoft is also introducing a new Defender Update Service as part of the change. Following installation of the first update, devices will automatically create a new directory located at %ProgramData%\Microsoft\Microsoft Defender\Defender Update. Microsoft notes that restarts may occasionally be necessary in case of "rare" failure scenarios. For most organizations, the tech giant says no action will be required as long as Microsoft Update is already permitted within their update management strategy. Admins who rely on manually deployed update packages, however, will need to adjust their processes to ensure the new Defender update package is included. Microsoft also recommends reviewing internal documentation and notifying helpdesk and security operations teams about the updated delivery mechanism to avoid confusion during the transition. As a prerequisite, the tech giant notes that systems must be running Sense version 10.8798.25857.1000 or later and have one of the following Windows updates (or later) installed: Win11 24H2 KB5062660 (2025-07 Cumulative Update Preview) Win11 23H2 KB5062663 (2025-07 Cumulative Update Preview) Win11 22H2 KB5062663 (2025-07 Cumulative Update Preview) Win10 22H2 KB5062649 (2025-07 Cumulative Update Preview) Win10 1809 KB5063877 (2025-08 Cumulative Update) Server 2019 KB5063877 (2025-08 Cumulative Update) Server 2022 KB5063880 (2025-08 Cumulative Update) Server 2025 KB5063878 (2025-08 Cumulative Update) As always, organizations should verify that their update policies align with the new servicing approach before the broader rollout reaches all supported Windows platforms later this year. In case of major problems, the EDR update can be rolled back to the inbox version stored in %ProgramFiles%\\Windows Defender Advanced Threat Protection (ATP) using: MpCmdRun.exe -RevertMde -Product Edr -ToVersion Inbox For those who have access to the Microsoft 365 Admin Center portal, you can view the message here under ID MC1381119.
  • Recent Achievements

    • One Month Later
      DJC50PLUS earned a badge
      One Month Later
    • Week One Done
      DJC50PLUS earned a badge
      Week One Done
    • Proficient
      Eric Biran went up a rank
      Proficient
    • Dedicated
      Conjor earned a badge
      Dedicated
    • Week One Done
      Windows Guy earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      493
    2. 2
      PsYcHoKiLLa
      248
    3. 3
      Steven P.
      73
    4. 4
      +Edouard
      69
    5. 5
      neufuse
      68
  • Tell a friend

    Love Neowin? Tell a friend!