Interestingly, blocking remote fonts on WordPress fixes Bold lettering from not appearing. :)

dear Delta Airlines, you suck

go to delta.com, try to book a ticket

any route will do, but make it roundtrip

pick your first flight... and it dies there

their toxic bloaty framework DOES catch the error:

ReferenceError: PointerEvent is not defined- currentUrl: delta.com/flight-search/search-resu…1f01cda-5a2f-4f72-bf8b-d44b881ec2dc, referringUrl: delta.com

it DOES work on FF91ESR

their airplanes might be old (they still fly the DC-9 descendants!), but their website is way too modern

developer.mozilla.org/en-US/docs/Web/API/PointerEvent ah yeah, that requires FF59 :/

and some features remain unimplemented, and only Chrome™, MS Chrome™ and Chinese Chrome™ fully support that API

"The PointerEvent interface represents the state of a DOM event produced by a pointer such as the geometry of the contact point, the device type that generated the event, the amount of pressure that was applied on the contact surface, etc."

uh, that's WAY too overkill for an airline booking site - all they need is to process a click (or tap), nothing else!

Oh wait, you CAN pick a fare if you click on the cabin name on the schedules - it will open a DIV with a photo of their old planes and a SELECT FLIGHT button that works!

as I not traveling, I can't ensure that Delta will take your money and let you fly on them from SeaMonkey, but that might work...

frg i just realized something... when I set up the xref I set it up in the traditional comm setup.. but it occured to me you might be using comm under mozilla now

so i was wondering if you wanted it changed to how it actually is

or retained for better cross-reference with 52

i figure you guys are still in the habit of doing the translation in your heads automatically when you check shit like this but I wanted to make sure it is setup how you want it

personally at this rate I dunno why you are keeping seperate repos anyway .. just simplfy and merge the two

oh wait.. it IS a proper comm build

well in that case I can make that happen pretty simply

oh my mistake yeah

tomman: " Oh wait, you CAN pick a fare if you click on the cabin name" <-- maybe it needs a cabin so it can populate the pressure value in the PointerEvent? (Sorry, sorry)

Pointer Events could probably be activated. Not sure what is still missing but we are far into 58 here already. Bug 1411467

dom.w3c_pointer_events.enabled?

ah yes, that's what bug 1411467 toggles

Doubt the remaining issues will burn the house down.

CaptainTobin comm/* would be correct but I can "translate" mentally. There might be some minor overlap in the directories.

frg_Away: i figired out WHY i did that

becaus ethe default branch

the one that should be used as a trunk?

IT is still in its orginal comm configuration cause that is how it landed in the repo when it was created

but an ACTIVE branch shows jcrammer's handywork

so if you want it how it is layed out tree wise tell me how it is.. mozilla/comm?

or how doe sthat work now

CaptainTobin comm-release is as comm under the mozilla-release source. The mozilla directory is gone unless you name the root directory mozilla.

where is comm under mozilla tho

is it comm/?

So it is

/browser

/toolkit

/blablabla

/comm/mail

/comm/mailnews

kk

/comm/suite

/comm/blablala

so comm is cloned to a dir called comm

no problem

correct

frg_Away: have you considered dropping comm and just having the one repo with it all like it was?

I can make it happen if you desire it

from a repo management aspect nothing will change cause i would merge comm ontop of mozilla after first removing any conflicts before hand.. configuration is simple too.. go through and make everything actually obey MOZILLA_DIR/MOZILLA_SRCDIR properly THEN fix it in mozilla which is shit i already did years ago .. also exclude mail cause there is literally nothing you are using from it

but yeah i will fix the xr for you today at some point

CaptainTobin for one minute but mozilla is a monster and operations on it slow. Really prefer it this way. Also we update suite and then still push to comm-central. Makes patch management easier. Maybe one day when mozilla is no more.

that's the thing .. as a comm app already setup to use the right variable unlike say if you were doing firefox.. and it is just some path and build files nothing that would really affect porting or repo operations but i do understand.. BUT if you guys do decide to venture that way let me know cause I have done it both gitwise and buildwise back and forth

I think I am gonna split all the third_party libs out of the codebase into another repo given I moved em all anyway and ain't gonna move em back simple patching is out the window

It not about style but survival mostly. Makes backporting and forward porting easy and takes less time rebasing patches. When we are at esr 78 level and have python 3 compatibility I will start ripping out build stuff for android and telemtry in earnest.

i am gonna include the php interpreter with a customized version of mozillabuild

I have already figured out how to get a base of mozillabuild 3.4 still able to be like 2.2 it is all in the batch files so i am gonna have an msys1 package with a new main startup script with a menu to access 2.2 mode with visual studio or 3.4 mode where it guesses THAT way once I transition to newer vs support i don't have to redo my tools .. again

of course getting to a point where i can build from inside of msys2 is a huge goal