Jump to content

My Browser Builds (Part 3)

roytam1
 Share

Recommended Posts

RamonUn

RamonUn

Posted
Posted (edited)

There is an issue with accessibility option for New Moon related to the caret position.

I realized this while developing an "extended key menu" to be able to type easily accentuated characters with any keyboard layout. For this I need to popup a menu at the caret position, however the focused program needs to have a native windows caret in order for this to be possible (using GetGUIThreadInfo()), and it is not the case with all of yours browsers.

The same problem applies to the Windows Magnifier that centers on the caret position as soon as you type in something, also using GetGUIThreadInfo() function (I think).

A native Windows caret is created according to the UXP source as soon as accessibility option is activated, This is needed for the magnifier, so it works mostly fine on IceApe-UXP as well as on Serpent. There are some bugs here and there but I will talk more about them later. There are also Other calls to ::SetCaretPos() in "widget/windows/IMMHandler.cpp" and in "widget/windows/TSFTextStore.cpp".

The biggest Issue is with PaleMoon28, for some reasons the Magnifier is unable to track the caret position. I assume it ends up not being created. Could this be fixed?

I tested a few of your builds:

1) IceApe-UXP: OK

2) bnavigator: OK

3) Serpent: OK

4) KM-Goanna: OK

5) MailNews: OK

I did not test other browsers, so for Me only NewMoon seems to have the problem.

There are a few bugs when using the magnifier even with those working browsers:

1) it seems that a wrong value of Caret position is given when you navigate through text with left/right arrows, or when you press origin/end keys. It also seems it is updated only every few lines when using the up/down arrow lines.

2) it also seems that the caret  position is updated only when at the end of a line and when typing a character. This has the advantage of making the text less moving in the magnified window but it also means that you often are unable to see what you type in the Magnifier.

Do you have any clue why Magnifier completely fails to track the caret on NewMoon? could be this fixed?

I think this is a bit problematic because I do know a couple of guys that need the Magnifier.

PS: I tried RetroZilla and here everything is perfectly flawless in this regard!

 

Edited by RamonUn
Clarified a little
Link to comment
Share on other sites

roytam1

roytam1

Posted
  • Author
Posted
3 hours ago, RamonUn said:

The biggest Issue is with PaleMoon28, for some reasons the Magnifier is unable to track the caret position. I assume it ends up not being created. Could this be fixed?

because newmoon is built with "--disable-accessibility" switch.

2
Link to comment
Share on other sites
RamonUn

RamonUn

Posted
Posted

I forgot to check the configure options, I can see them now in about:buildconfig. Thanks for the clarification!

Any reason you disable them on NewMoon? I do not think it would impact performances, would it?

I do not have a build environment so I cannot check, nor test some fixes for the bad caret tracking even when accessibility is enabled.

Link to comment
Share on other sites
roytam1

roytam1

Posted
  • Author
Posted
1 hour ago, RamonUn said:

I forgot to check the configure options, I can see them now in about:buildconfig. Thanks for the clarification!

Any reason you disable them on NewMoon? I do not think it would impact performances, would it?

I do not have a build environment so I cannot check, nor test some fixes for the bad caret tracking even when accessibility is enabled.

because official builds don't have this enabled, newmoon28 front-end code with accessibility-enabled are totally untested

2
Link to comment
Share on other sites
VistaLover

VistaLover

Posted
Posted

Sorry for posting this here :P, but since several roytam1 offerings were also previously appearing on the "eclipse" forums ;), do any of you know what happened to "https://board.eclipse.cx/" and where, per chance, they have moved on to? 
Google cache has archived a snapshot taken on Apr 2nd, but currently all that is returned on the domain is an "Account Suspended" error message... :( :angry: 

Link to comment
Share on other sites
soggi

soggi

Posted
Posted

The mirror of latest BNavigator, Firefox 45ESR, IceApe, IceDove, K-Meleon 1.5.x/74/76, MailNews 52, New Moon 26.5/27/28 and Serpent 52/55 builds by @roytam1 has been updated -> soggi.org - tools.

changelog:
- added latest BNavigator 0.9 20220402 build
- added latest IceApe 52 20220402 build
- added latest IceDove 52 20220402 build
- added latest K-Meleon 76 20220402 build
- added latest MailNews 52 20220402 build
- added latest New Moon 27 20220402 builds
- added latest New Moon 28 20220402 builds
- added latest Serpent 52 20220402 builds
- added latest Serpent 55 20220402 builds

---------------------------------------------------------

21 hours ago, NotHereToPlayGames said:

I'm curious if there are any Roytam Followers that know these builds enough to recommend which one is "optimum" for Windows 7?

Maybe I'll be stoned...but I would recommend the latest Pale Moon (current is 29.4.5.1).

kind regards
soggi

Link to comment
Share on other sites
nicolaasjan

nicolaasjan

Posted
Posted
3 hours ago, soggi said:

Maybe I'll be stoned...but I would recommend the latest Pale Moon (current is 29.4.5.1).

kind regards
soggi

There is a chance that Moonchild will stop supporting Windows 7 when Extended Security Updates ends (January 10, 2023).

I hope New Moon will keep working on it.

1
Link to comment
Share on other sites
soggi

soggi

Posted
Posted (edited)

Of course, like support for WinXP ended with Pale Moon 26.5 back then.

But I have to say, that I installed latest Pale Moon on a Win7 machine some days / couple of weeks ago and really was surprised again (like years ago when I switched from FF52 to PM25/26) - I really like this handy and fast classic UI, which can't be fully restored with latest FF ESR.

kind regards
soggi

Edited by soggi
Link to comment
Share on other sites
VistaLover

VistaLover

Posted
Posted

@roytam1 : I just, accidentally, stumbled upon yet another UXP (longstanding) bug, that manifests itself on GitHub issues; the bug is there regardless of whether the relevant github-wc-polyfill extension is installed or not... I used recent Serpent 52.9.0/UXP builds to test. 

STR:

1. Load a new, fresh, Serpent 52.9.0 profile (default prefs, no add-ons)
2. New Tab => Paste & Go: https://github.com/JustOff/github-wc-polyfill/issues/45#issuecomment-1066105393
NB: It is imperative the body of the issue comment contain at least one active link (not only in the form of a plain "https://*" string, but any type of "linkified" string)
3. Place the cursor on top of the active link, then right click to access the browser's context menu; so far, so good:

pPERZwo.jpg

4. Move the cursor away from the context menu, left-click to make the menu go away...
5. Repeat step 3; right-clicking this second time results in the whole content of the issue comment to get selected:

vVykE0r.jpg

I have successfully reproduced this bug with many GitHub issue-comments, with/without the gh-wc-pf add-on...

Trying to find a regression range for this bug, I've spent considerable time and effort which, in the end, got me all the way back to mid-2020:
Last Good build (without the bug):
basilisk52-g4.6.win32-git-20200530-d6ba7ac-uxp-1cecef624-xpmod
First Bad build (with the bug as described above):
basilisk52-g4.6.win32-git-20200606-547d236-uxp-fdb918dea-xpmod

Hopefully, the cause could be narrowed down...
Obviously, this isn't a deal breaker, however little annoyances like this one make me use more often either 360EEv11/v12 for GitHub (with extra polyfills applied there via @InterLinked 's extension), while I'd be happy to cling on to Serpent 52 for most of my on-line tasks... ;) 

Many thanks :)

1
Link to comment
Share on other sites
soggi

soggi

Posted
Posted
15 hours ago, nicolaasjan said:

There is a chance that Moonchild will stop supporting Windows 7 when Extended Security Updates ends (January 10, 2023).

I hope New Moon will keep working on it.

 

6 hours ago, soggi said:

Of course, like support for WinXP ended with Pale Moon 26.5 back then.

But I have to say, that I installed latest Pale Moon on a Win7 machine some days / couple of weeks ago and really was surprised again (like years ago when I switched from FF52 to PM25/26) - I really like this handy and fast classic UI, which can't be fully restored with latest FF ESR.

I have to add this to my previous post...

The whole thing arose from the circumstance that Pale Moon for XP wasn't tolerated anymore in the Moonchild / Matt A. Tobin universe and has been banned therefor. This was a very wrong decision, in my opinion. Why to work against fellows in this small OSS browser niche of Pale Moon? I still don't get it... There are chances of benefit for both sides, untapped potential. I understand that WinXP and prior are EOS long since, but Pale Moon XP / New Moon (with a *unsupported* mark, for my sake) could be released with latest Pale Moon under one umbrella. This would be a win-win situation.

I hate people... head -> table, head -> table, head -> table...

kind regards
soggi

1
Link to comment
Share on other sites
Anbima

Anbima

Posted
Posted

Hello,

currently I use mypal, but here it probably will not give any updates anymore. Therefore, I have to take care of an alternative.

What Browser ist better for Win XP Pro with SSE, SSE2, SSE3 and SSE4A:

New build of Serpent/UXP for XP or NM28XP build?

How I can in NM28XP change google as default search engine and how I can change to german language?

Link to comment
Share on other sites
NotHereToPlayGames

NotHereToPlayGames

Posted
Posted (edited)

This is the best answer I can find for you  --

spacer.png

 

No two people on the planet use their web browser the same exact way.

One user only needs "red and blue" so the "purple" web browser fits 100% of their needs but that web browser fails at "yellow".

Et cetera...

Edited by NotHereToPlayGames
1
Link to comment
Share on other sites
nicolaasjan

nicolaasjan

Posted
Posted
1 hour ago, Anbima said:

How I can in NM28XP change google as default search engine

Put the file "google.xml" in your profile folder in the subfolder "searchplugins":  

<SearchPlugin xmlns="http://www.mozilla.org/2006/browser/search/" xmlns:os="http://a9.com/-/spec/opensearch/1.1/">
<os:ShortName>Google</os:ShortName>
<os:Description>Google</os:Description>
<os:InputEncoding>UTF-8</os:InputEncoding>
<os:Image width="16" height="16">data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABAAAAAQCAYAAAAf8/9hAAACaUlEQVQ4jXWTzUuUURSHrzALtfob/BO0nLHU1cwISitTM6WPjeCmTR9EtBR0gqiV+ZEmRCh+TBA0WFEZtnEhkoPZaC2yCKacERPeeZ2Z+95znxZjQyr+NhcO5zyc+zvnKHVArt45JSUyaJVaV9bmxBgtnnw1Yoa0pupgflFLyaXyEuSRWLEcIWsEETNSsVFRuq84maTcGPMBwOZzZKITbHdfJtVYT6qplu3uS+xOjWPz+QIIMx9LxsqLABEzCiCbv9nu6iAdCpAK1ey9flINftLhGnZuXy12o3VuRCmllE9TBWLJ5tnqaicVCpBqqsMdHUCvLJNfiZMZfUj6YjPmx0YRYIzg81GpBBkCMPF+tpqr2GyqxVuNHzbAmEMhERlUStl1AL0YQL8ox53pOcrDwwDLmhIkD6DfHcOb82HSs/uSwn0OwYhDsNch1OsS7M1wZzq3Z6bNKmOtBvDeH8fM+TBbsX2AYJ9LuM8h3OsQ6nMJRhxuTOz+A+QU8AXAWzzN5tsTxOL3j2y553mOcMTh3mx+L2LXlBg9DPD92yhN0bOcmTnPx9TqoeL1pEfjXYdwxGE+UTBUiwwqrd2TWGuzXo4Lr64RmGqlPtpJ//JTllIJ4ukEY5+jNDwZJhjZoXtsFxGwWKszurDa2sgIwKabpuPldfxTLVRPthGYbsE/3Ub1VCv+yRbOPXvArz9SmEAJg8VNhIpSY5gHyHua8bUYV97conamg7rpdjpf3+Txpyiu5xZ+7pn5BRbK9t3DTxbKtMmNKIUcPXixRhjaqDhwTP9Lk6kyRoawNmGtzVqrstaSECMDGXTlwfy/HKvn5Yvb6ysAAAAASUVORK5CYII=</os:Image>
<os:Url type="text/html" method="GET" template="https://www.google.com/search" resultDomain="google.com">
  <os:Param name="q" value="{searchTerms}"/>
  <os:Param name="btnK" value="Google+Zoeken"/>
  <os:Param name="source" value="hp"/>
</os:Url>
</SearchPlugin>

Made this with the extension "Add to Search Bar" from Firefox in the old days (not available any more).

Just right-click in a search field on a site and click "Add to Search Bar..." :)

If you can't find it, I have it here in my Dropbox account.

1
Link to comment
Share on other sites
Anbima

Anbima

Posted
Posted
4 minutes ago, NotHereToPlayGames said:

No two people on the planet use their web browser the same exact way.

One user only needs "red and blue" so the "purple" web browser fits 100% of their needs but that web browser fails at "yellow".

Et cetera...

For me it is important that modern sites work. Since a lot is done with JS, a good JS engine would be an advantage.

Or how are these browsers differ?

Link to comment
Share on other sites
NotHereToPlayGames

NotHereToPlayGames

Posted
Posted
8 minutes ago, Anbima said:

For me it is important that modern sites work. Since a lot is done with JS, a good JS engine would be an advantage.

You will find that NONE of the web browsers in this thread will match that criteria "out of the box".

I'll return to show some screencap's as this will take a few minutes to answer fully.

1
Link to comment
Share on other sites
Guest
This topic is now closed to further replies.
 Share
Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...