Skip to content

Conversation

@robertbryer
Copy link
Collaborator

https://bugzilla.mozilla.org/show_bug.cgi?id=1502610

This will cause the positioning to be slightly off and should be removed when the bug is resolved.

Copy link
Collaborator

@nigelmegitt nigelmegitt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We need to leave a comment about this change, and a link to the Firefox bugzilla ticket, so future us can understand why this change is here.

I think it would also be nice to minimise the impact by only using the override 0px value for marginLeft on ee when ipd === "rl" and marginRight on ee when ipd==="lr" which I think should work. What do you think @robertbryer , too complicated?

Copy link
Collaborator

@nigelmegitt nigelmegitt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, that looks good aside from the blank line deletions. I'll also load this up locally and verify it fixes the issue in the expected way for me.


// Start element
if (context.ipd === "lr") {

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's a bit of an idiomatic code style thing, but these blank lines are deliberate and endemic in the library, so we should probably keep them. I think I once got a pull request bounced back by @palemieux for breaking the coding style like this, and it looks like it would be good to contribute this workaround back to sandflow/imscjs if we can.

@nigelmegitt
Copy link
Collaborator

Verified that the fix works on Firefox, and is not applied on Chrome.

@nigelmegitt
Copy link
Collaborator

Don't we normally check in the built version?

@robertbryer robertbryer merged commit 830a52b into smp-master Jul 3, 2023
@robertbryer robertbryer deleted the negative-margins branch July 3, 2023 13:25
@robertbryer
Copy link
Collaborator Author

Typically no, only CI should be publishing build artefacts; really it should be uploading to npm instead of git pushing the dist folder, but there was a lack of clarity on npm licences at the time we started this project.

nigelmegitt added a commit to nigelmegitt/imscJS that referenced this pull request Oct 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants