Hi developers,
this is a longstanding bug:

With facing pages documents on EVERY document page there is a zone where jumping of objects will happen.

I call this the jump zone. All objects on a page that will jump are clearly inside the page's area. The bug has nothing to do with rounding errors where object edges are at the edge of a page.

The objects should not move if pages are added or removed, if numbering of pages is changing. Nevertheless they do. Always. Unless, the zone has a width of zero.

Below all the details.

What is a jump zone?
If horizontal values for left and right margins differ, there is a BUG that in effect forms a zone on the page.
I call this zone JUMP ZONE because objects that touch the zone with their edges could jump horizontally.

When will objects jump?
1. When a left-hand page becomes a right-hand page OR a right-hand page becomes a left-hand page.

1. When a left-hand page becomes a right-hand page and later when a right-hand page becomes a left-hand page again.

This could happen within a single InDesign document open.

WARNING:
It could even happen to InDesign documents that are not visibly open.
That's with InDesign documents that are part of a InDesign book file.
The book file's feature with auto-numbering pages can do this even if no document is visibly open.
The damage is done if auto-numbering took place AND the book file is saved.

How large is the jump zone?
The height of the zone is the height of the page.
The width of the zone can be calculated:
inner margin MINUS outer margin

How large is the jump?
The width of the jump zone.

Where is the jump zone positioned?
Positive value: The zone is at the spine of the page.
Objects that touch the zone jump towards the spine.

Negative value: The zone is at the edge of a page away from the spine.
Objects that touch the zone jump away from spine.

What versions of InDesign are affected?
All versions CC up to InDesign 2020, Mac OS X and Windows.
InDesign CS6, Mac OS X and Windows.

Possibly also InDesign CS5 and CS5.5, Mac OS X and Windows.
I did not test this.

How can I avoid jump zones?
Make right and left margin values the same!

Are there workarounds if I cannot avoid jump zones?

1. Anchor objects
   that touch the jump zone to text frames that do not touch the jump zone.
   Nested objects will not jump if the parent objects are not touching the jump zone.




2. Group an object
   to another one that is touching the top or the bottom edge of the page.
   Tests are showing that objects will not jump if they touch the bottom OR the top of the page.
   ( OR both, bottom and top edges of the page .)

Other things to consider about moving objects?
The following is independently of jump zones:
Objects could move to other pages if their edges touch exactly the horizontal edges on pages in facing pages.
Depending on the version of InDesign this could also happen with objects touching the spine.
Reason: Rounding errors.

What can provoke all this?
1. Add or remove an odd number of pages
so that left-hand pages become right-hand pages and vice versa.

1. Renumber start pages of sections
   so that left-hand pages become right-hand pages and vice versa.

Note:
Every document has at least one section by default.
The start of that section is the first page in the document.

More details at Adobe InDesign Forum:
https://community.adobe.com/t5/indesign/bug-in-book-s-update-numbering-feature/m-p/10774458#M166408

InDesign 2020 documents attached here.
See screenshots and further comments at Adobe InDesign Forum:
https://community.adobe.com/t5/indesign/bug-in-book-s-update-numbering-feature/m-p/10774596#M166420

Download link to all test files on my Dropbox account:
https://www.dropbox.com/s/duov096cu2q481l/Jump-Zones-Explained-Facing-Pages-Documents.zip?dl=0

Regards,
Uwe Laubender

( ACP )

PS: Why does InDesign Uservoice not permit to attach files with suffix .indd ?
Message: "Invalid file type: .indd files not allowed."
Isn't that rather absurd?

I'm using a Mac and running Catalina, have ID 2020. Yesterday, an existing file of 33 pages stopped allowing me to save it. I had no idea it wasn't saving and lost hours worth of work by the time I realized what was happening. I tried starting a new document and pasting the text into it, but same problem. I started a new document again and it allowed me to save immediately, but the second I dropped in text (different text this time), I lost the ability to save the file. I can export to PDF or IDML, but cannot simply save the file.

1. Adobe InDesign 15.0.1 x64 (Windows 10)


2. Facing pages document. I create a master page that includes two text frames per page--creating a two column spread on each page. I designate the leftmost frame as the primary text frame, and then manually link it to the frame just to its right. That frame is then linked to the leftmost frame on the right side page, and that one is linked to the frame furthest to the right. So the frames are linked, from left to right: frame 1 is primary, which is linked to frame 2, then to frame 3 (on the other page) and then to frame 4.

Using the pages panel, I manually insert four pages into my document, assigning the new master page to these pages. The first three text frames are threaded correctly, but then the threading goes completely haywire.

1. I would expect the new blank pages to replicate the text threading order that I created on my master page.




2. The text threading goes wacky. I have included an image to demonstrate.

This seems similar to the problem posted in this Bug report (34661228-based-on-master-pages-don-t-inherit-primary-text-f.html) however on the document pages my text frames ARE threaded, just not threaded in the same manner as they were on my master pages. Plus, I am using a much later version of InDesign than the one that fixed that particular problem.

I'm using Indesign 15.0 on MacBook Pro (Retina, Mid 2012) running Mojave version 10.14.6

I'm experiencing a bug with the Source Serif Pro font , which I use extensively in a particular project.

I open an existing document, and the text in Source Serif Pro looks as you'd expect it to. When I start to edit the text however, it all jumps down as if the baseline settings of the text frame has been changed (although checking in the settings confirms they haven't been).

Copying and pasting the frame, or the text into a new frame, doesn't help.

It only happens with Source Serif Pro (all weights) - if I change the font, even to other Adobe Fonts it doesn't happen. It also happens in new documents.

It may be worth mentioning that a colleague works on the same Indesign files on a PC (we share the files via Dropbox) but he doesn't experience the issue.

We both share another related bug with Source Serif Pro in that quotation marks just display as 'straight' even though 'use typographer's quotes' is turned on in preferences. This can't be fixed through the Glyphs panel either.

My feeling is it's something to do with this particular font being used a lot over 2 different platforms.

Thanks

Version: 15.0.2

Steps to reproduce the issues:
I was teaching 3 students on 15.0.2 (all on Windows) how to create a new document. We set up a 12-page file and specified 3 columns and changed the top margin in the New Document dialog box. With the preview checkbox on, body page 1 did not reflect the changes. We could see the bleed and slug lines appearing when defined. We could also see the A in the corner of the the body page 1 icon in the Pages panel, indicating that A-Master was assigned.

Expected result
When you define a new document with Preview enabled, you should be able to see the margins and columns as defined on the first page, behind the dialog box before (and after) you click on OK.

Actual result:
After clicking on OK, we discovered that the margins and columns were defined and visible on the A-Master and body pages 2-12. We had to manually re-apply the A-Master to Body page 1. This happened to all three students.

It is working as expected on my Mac 10.15.3.

I am using CC2019 and the have the same issue in CC2020. I have mysterious areas of whitespace that I can't use appearing on my pages. Please see the attached file. The file is part of a book. Page 110 (relative to book's start, the third spread in the file) is where the trouble starts.

I don't mean to be a nuisance but sorting this out is rather urgent. I am going to destroy the document and start again out of desperation.

Kind regards
Mike Howell

I have tried reducing image sizes.
I have tried analysing the story.
I have adjusted keep options.
I have checked the text frame threading.
I have looked for overlapping frames.

I still can't work it out.

Kind regards
Mike Howell