The Un-Official Proxomitron Forum

Full Version: Menu and Important Info missing
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2
In Firefox33, The Sidki menu without.
Confirmed. Console shows new javascript errors. May be Firefox bug or true script error.

Code:
TypeError: prxO.oNce.ncBody is not a function prxbx.com:64
TypeError: PrxRLsetTimeout is not a function proxjs-full.js:1011
Hi !

Ever since the firefox got upgraded to version 29 ( UI Australias), Display of code, site specific js code etc.. at the bottom of webpage have stopped becoming visible.

Will anyone be able to help me how to make them visible again..

I am using Sidki's latest filters.

Thanks
Jurang
(Jan. 07, 2015 02:27 PM)jurang Wrote: [ -> ]Ever since the firefox got upgraded to version 29 ( UI Australias), Display of code, site specific js code etc.. at the bottom of webpage have stopped becoming visible.

Attached files should help but there is still work to do. Also, some old versions of Firefox and Opera are not supported. I'm not sure which old versions.

Rename the old files before adding these. Files are probably located in "html\sidki_h_???????"

HTH

This post will be merged with http://prxbx.com/forums/showthread.php?tid=2176 later
Dear JJoe,

Thanks for your reply. After replacing the old two files with the new ones ( attached with your reply),, all the display codes, menu etc are back at the bottom and it is working as it should. Hope that is all is needed for firefox versions 29 and above.

Thanks again for your great help and support.

Best regards
Garcot
on a semi-related note, and this isn't a new problem, the new .js files do this, the old .js files did this

if you go here - http://finance.yahoo.com/news/inplay-bri...39997.html

note that the footer notes (hits, site, cookies, timer) are at the TOP of the page instead of at the bottom - is this "fixable"?
(Jan. 10, 2015 03:25 AM)ProxRocks Wrote: [ -> ]note that the footer notes (hits, site, cookies, timer) are at the TOP of the page instead of at the bottom - is this "fixable"?

The quickest solution (tho not necessarily the best) I can offer is to open "proxcss-general.css", find

Code:
div#pr0xDom-Div
{
  clear: both;
  position: relative;
  padding: 3px 0 3px 7px;
  direction: ltr !important;
  float: none !important;
  background: transparent;
  border-style: none;
  outline-style: none !important;
  white-space: normal !important;
  text-align: left !important;
  text-decoration: none !important;
  width: auto;
  height: auto;
  visibility: visible;
  z-index: 100000001;
}

Change it to suit. Like

Code:
div#pr0xDom-Div
{
  clear: both;
  position: fixed;
  padding: 3px 0 3px 7px;
  direction: ltr !important;
  float: none !important;
  background: transparent;
  border-style: none;
  outline-style: none !important;
  white-space: normal !important;
  text-align: left !important;
  text-decoration: none !important;
  width: auto;
  height: auto;
  visibility: visible;
  Bottom: 5px;  
  z-index: 100000001;
}
These 'fixes' are intended to be temporary.
sweet, thanks...

the way i see it, it's "permanent for now"...
my entire Prox folder is basically "temporary" as it changes whenever something dictates changes Smile!
i have noticed that the footer notes are now at the bottom CENTER of some pages (ie, right here at prxbx)...

no real problem, i'd rather have that and be CONSISTENTLY at the BOTTOM...

but now the wheels are turning -
you know how the lower-right triangle-within-a-circle menu-access icon only appears during a mouse-click then disappears with a scroll?

i wonder if perhaps the footer notes should appear and disapper to the left of that menu-access icon instead of as a constant-on footer note?
still under construction, but i've been experimenting with the footer-note for better usability/consistency

seems that a FIXED position offers the best consistency
and the bottom RIGHT corner is the least obtrusive
but then the flyover is pushed off of the page Sad

so i'm trying to FIX the footer to the RIGHT but have the flyover on the LEFT as opposed to "static" above the footer

or keeping it all (footer and flyover) on the LEFT but it "timing out" and hiding itself

or keeping it all on the LEFT but it hiding until "activated" by hover or by same click that accesses the lower-right menu

or display as part of the click-to-access menu instead of as its own entity
Sidki Proxo menu missing on Fx 35 and SeaMonkey 2.32 on Windows 8.0 Pro.

Sidki Proxo menu works on IE 10 though. But I don't like using IE.

Sidki Proxo menu works on MANY websites on Pale Moon 25.2 (x64). It does NOT work on my home site dslreports.com. (In fact, Proxo is so bad there now that I have to bypass it most of the time as javascript won't work right there with Proxo enabled).

On Windows 10 Preview, Proxo menu works fine, even at dslreports.com, on Fx 31.4 ESR.

On Windows 10 Preview, on IE 11 Edge Mode Proxo menu doesn't appear on any site but that doesn't surprise me as IE 11 for Win 10 is in early stages of development.

I miss it on Fx35 Portable which, to my surprise, with CTR extension I really like. So, while I also have Fx 31.4 ESR on Windows 8 Pro where Proxo menu works, I prefer using Fx35 and miss the menu.
Thanks for the tip to send "footer notes" back to the bottom.
But simply adding a "bottom" attribute
Code:
div#pr0xDom-Div
{
...
bottom: 5px;
z-index: 100000001;
}
was not enough in my case. The display-line was written at the bottom of the screen (not page bottom), and moved up when scrolling.
I had to add "!important" to the "position" and "bottom" attributes, like this:
Code:
div#pr0xDom-Div
{
  clear: both;
  position: relative !important;
  padding: 3px 0 3px 7px;
  direction: ltr !important;
  float: none !important;
  background: transparent;
  border-style: none;
  outline-style: none !important;
  white-space: normal !important;
  text-align: left !important;
  text-decoration: none !important;
  width: auto;
  height: auto;
  visibility: visible;
  bottom: 5px !important;
  z-index: 100000001;
}

HTH.
Have been solved, thanks!
Pages: 1 2
Reference URL's