Search bar changed in beta1 Topic is solved

This board is for discussions, bug reports, etc. for pre-releases of the v28 milestone building on UXP.

Moderator: satrow

User avatar
Pale Moon Rising
Knows the dark side
Knows the dark side
Posts: 3277
Joined: Tue, 06 Oct 2015, 16:59
Location: Los Angeles CA USA

Re: Search bar changed in beta1

Unread postby Pale Moon Rising » Thu, 05 Jul 2018, 03:17

SpockFan02 -- More problems with the search bar that I'll need your help on that needs additional CSS code beyond what you've given me.

This is what I get now (more text at the end is messed up with text shadowing):
more CSS required on search bar.png
Click on to enlarge
... makes me wonder how much more text can be displayed on the search bar that needs fixing.

The text will display either "Reached end of page, continued from top" like in the screen-shot or "Reached top of page, continued from bottom".

This is what I've got which works for everything else except the last text I didn't know would occur:

Code: Select all

.findbar-find-next,
.findbar-find-previous,
.findbar-button > .toolbarbutton-text,
.findbar-button > .checkbox-label-box,
.found-matches { text-shadow: 0 0 0 !important; }

.findbar { background color: rgb(0,0,0) !important; }
Hopefully the CSS code needed to fix this new text problem will cover whatever else might occur in the find bar. :think:
Current Pale Moon(x86) Release | WIN7(64-bit) | I3 CPU, 2.53 GHz, 4G RAM

Good judgment comes from experience and a lot of that comes from bad judgment. - Will Rogers

Knowing Pale Moon is indisputably #1 is defined by knowing the totality of browsers. - Pale Moon Rising

User avatar
SpockFan02
Lunatic
Lunatic
Posts: 459
Joined: Sun, 24 Sep 2017, 16:35

Re: Search bar changed in beta1

Unread postby SpockFan02 » Thu, 05 Jul 2018, 05:49

Add .findbar-find-status to the text-shadow rule to get those messages.

You could also use

Code: Select all

.findbar-container * { text-shadow: 0 0 0 !important; }
to catch anything else in the findbar, and it shouldn't have side effects unless something in there is actually supposed to have text shadow, which I don't think is the case.

User avatar
Pale Moon Rising
Knows the dark side
Knows the dark side
Posts: 3277
Joined: Tue, 06 Oct 2015, 16:59
Location: Los Angeles CA USA

Re: Search bar changed in beta1

Unread postby Pale Moon Rising » Thu, 05 Jul 2018, 06:47

^ Thanks again SpockFan02 -- works great! :thumbup: --- I also added the "catch-all" (wildcard "container") line as well just in case ;) (which should take care of it for good!). :clap:
Current Pale Moon(x86) Release | WIN7(64-bit) | I3 CPU, 2.53 GHz, 4G RAM

Good judgment comes from experience and a lot of that comes from bad judgment. - Will Rogers

Knowing Pale Moon is indisputably #1 is defined by knowing the totality of browsers. - Pale Moon Rising

User avatar
SpockFan02
Lunatic
Lunatic
Posts: 459
Joined: Sun, 24 Sep 2017, 16:35

Re: Search bar changed in beta1

Unread postby SpockFan02 » Thu, 05 Jul 2018, 07:01

:thumbup: I'm happy to help.

FYI that catch-all works by selecting any element (the asterisk) that is within .findbar-container, and I found .findbar-container and all the other elements by using DOMi (DOM Inspector).

User avatar
Pale Moon Rising
Knows the dark side
Knows the dark side
Posts: 3277
Joined: Tue, 06 Oct 2015, 16:59
Location: Los Angeles CA USA

Re: Search bar changed in beta1

Unread postby Pale Moon Rising » Thu, 05 Jul 2018, 07:23

SpockFan02 wrote:....and I found .findbar-container and all the other elements by using DOMi (DOM Inspector).
Oh -- so that's how you find out what element names are used like the elements "button" and "find-status" that the find-bar uses besides the "container" element that is using the "*" wildcard for any element within the "container" element of the find-bar -- good to know, I'll check this out some more when I get the time. :thumbup:
Current Pale Moon(x86) Release | WIN7(64-bit) | I3 CPU, 2.53 GHz, 4G RAM

Good judgment comes from experience and a lot of that comes from bad judgment. - Will Rogers

Knowing Pale Moon is indisputably #1 is defined by knowing the totality of browsers. - Pale Moon Rising

User avatar
Moonchild
Pale Moon guru
Pale Moon guru
Posts: 22013
Joined: Sun, 28 Aug 2011, 17:27
Location: 58.5°N 15.5°E
Contact:

Re: Search bar changed in beta1

Unread postby Moonchild » Thu, 05 Jul 2018, 11:16

These style changes should all be fixed with Issue #568 (UXP).
Improving Mozilla code: You know you're on the right track with code changes when you spend the majority of your time deleting code.

"If you want to build a better world for yourself, you have to be willing to build one for everybody." -- Coyote Osborne

User avatar
Pale Moon Rising
Knows the dark side
Knows the dark side
Posts: 3277
Joined: Tue, 06 Oct 2015, 16:59
Location: Los Angeles CA USA

Re: Search bar changed in beta1

Unread postby Pale Moon Rising » Wed, 11 Jul 2018, 16:44

SpockFan02 wrote:.... I found .findbar-container and all the other elements by using DOMi (DOM Inspector).
I've installed DOM Inspector:
dom inspector.png
How do you first start it to use it? I see no button icons available anywhere in the browser and no "options" button for the extension in the add-ons list. Looking at this Introduction link: https://developer.mozilla.org/en-US/docs/Tools/Add-ons/DOM_Inspector/Introduction_to_DOM_Inspector I see where it says "When you first start the DOM Inspector..." but I see no way to do this. :?
Current Pale Moon(x86) Release | WIN7(64-bit) | I3 CPU, 2.53 GHz, 4G RAM

Good judgment comes from experience and a lot of that comes from bad judgment. - Will Rogers

Knowing Pale Moon is indisputably #1 is defined by knowing the totality of browsers. - Pale Moon Rising

User avatar
SpockFan02
Lunatic
Lunatic
Posts: 459
Joined: Sun, 24 Sep 2017, 16:35

Re: Search bar changed in beta1

Unread postby SpockFan02 » Wed, 11 Jul 2018, 17:52

Pale Moon Rising wrote:
SpockFan02 wrote:.... I found .findbar-container and all the other elements by using DOMi (DOM Inspector).
I've installed DOM Inspector: dom inspector.pngHow do you first start it to use it? I see no button icons available anywhere in the browser and no "options" button for the extension in the add-ons list. Looking at this Introduction link: https://developer.mozilla.org/en-US/docs/Tools/Add-ons/DOM_Inspector/Introduction_to_DOM_Inspector I see where it says "When you first start the DOM Inspector..." but I see no way to do this. :?
Tools --> Web Developer --> DOM Inspector, or ctrl+shift+I (cmd on Mac). You can also use Element Inspector to shift+right-click on any element to highlight it in the DOM tree, or InspectorWidget to click and do the same.

User avatar
Pale Moon Rising
Knows the dark side
Knows the dark side
Posts: 3277
Joined: Tue, 06 Oct 2015, 16:59
Location: Los Angeles CA USA

Re: Search bar changed in beta1

Unread postby Pale Moon Rising » Wed, 11 Jul 2018, 18:26

^ Thanks - not sure if I need the other two add-ons (this one make 38 extensions I'm now using)....

Off-topic:
Anyway - since an upgrade to my start.me page the former CSS code no longer works.

Using DOMi I am not getting the information to the right (specifically what I need pointed out) for the start.me start-page that I use:
missing info in DOMi interface.png
I'm figuring the top line (as illustrated below in the CSS code) has changed with the new upgrade they just rolled out causing all my CSS code below to not work:

Code: Select all

@namespace url(http://www.w3.org/1999/xhtml);

@-moz-document domain("start.me") {
  .flex.clearfix{display: none !important;}
  header#header{display: none !important;}
  article.widget{border-radius: 15px;}
  section#searchbar .wrapper{border-radius: 10px;}
  section#searchbar .button{border-radius: 10px;}
  .buttons #add-content{border-radius: 10px;}
  #header .buttons #me{border-radius: 10px; overflow: hidden;}
  /*#footer{display: none;}*/
  #footer-ad{display: none;}
}
Looking at the "Namespace URL" value it is "undefined", I'm figuring that the "@namespace urL" value (in parentheses above) needs to be different than what it was before so the CSS code will work as it did before. But the DOM Inspector isn't providing this information.... would using either of the two other extensions help in this regard?
Last edited by Pale Moon Rising on Wed, 11 Jul 2018, 18:27, edited 1 time in total.
Current Pale Moon(x86) Release | WIN7(64-bit) | I3 CPU, 2.53 GHz, 4G RAM

Good judgment comes from experience and a lot of that comes from bad judgment. - Will Rogers

Knowing Pale Moon is indisputably #1 is defined by knowing the totality of browsers. - Pale Moon Rising

User avatar
SpockFan02
Lunatic
Lunatic
Posts: 459
Joined: Sun, 24 Sep 2017, 16:35

Re: Search bar changed in beta1

Unread postby SpockFan02 » Wed, 11 Jul 2018, 18:31

Off-topic:
Pale Moon Rising wrote:... Looking at the "Namespace URL" value it is "undefined", I'm figuring that the "@namespace urL" value (in parentheses above) needs to be different than what it was before so the CSS code will work as it did before. But the DOM Inspector isn't providing this information....
Click on HTML in the tree, it'll show the namespace.
Pale Moon Rising wrote:... would using either of the two other extensions help in this regard?
No, they only provide alternate ways to activate DOMi and select elements.

Also, use the dropdowns in the top-left of the two panes to look at style information, etc.
Last edited by SpockFan02 on Wed, 11 Jul 2018, 18:37, edited 1 time in total.


Return to “Pale Moon UXP alpha/beta”

Who is online

Users browsing this forum: No registered users and 1 guest