Comment is moved after a method call if object is one or two characters long

Prettier 3.7.4
Playground link

--parser babel

Input:

a //
  .bla()

ab //
  .bla()

abc //
  .bla()

Output:

a.bla(); //

ab.bla(); //

abc //
  .bla();

Expected output:

a //
  .bla()

ab //
  .bla()

abc //
  .bla()

Notice how the method call moves to the first line if the object name is one or two characters long (looking at it from another angle, the comment is moving after the method call).

Why?

It shouldn't matter that the object name is only two characters or shorter. The comment should never be moved.

Why does this matter though? Because I'm trying to use the comments to preserve the indentation.

Why does that matter though? Well there's a very long related #7884 issue, but in my case, the motivation is that I am using the code for an interactive use (think hot reloading constantly), and I want to keep the chain method calls on separate lines to easily move them and comment them out.

But for Prettier the better argument is that it is surprising that changing the object name (imagine you start with abc, then change to ab) suddenly changes the code.

Note that the length of the comment does not impact the formatting.

Reproduce the formatting difference in the linked Prettier Playground using the Babel parser and the a, ab, and abc chained-call examples. Trace how line comments are positioned around these method calls, then verify that the expected formatting preserves the comment placement for all three object-name lengths.