microsoft / microsoft/azure-devops-extension-sdk

Work Item Form Group Height not setting to 100%

Open
#97 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
159
Forks
53
PR merge metrics
No merged PRs in 30d

Description

I am writing an extension that is extending the work item form, and adding a work item form group. I have a manifest contribution using the ms.vss-work-web.work-item-form-group type.

According to the documentation, if the "height" property is not specified, it will set the height to 100%. However that is not happening.

When I don't specify the height property for the contribution, it is clearly setting the height to "150px" upon inspection:
image

This is preventing me from setting auto grow related css styles so the height will dynamically adjust depending on the content rendered within the group/frame. I can see the height being inherited in the iframe level from the .external-content-iframe class is 100%. But that is only allowing the space to fill up to the 150px height set at the higher level (in above screenshot).

If I manually set the height on the contribution manifest, I can see the height property is set in a style tag at both the vss-contentHost div level and the iframe level:
image

So when the "height": property is omitted from the contribution manifest, perhaps it is only setting the height to 100% at the iframe level and not the parent vss-contentHost div level.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the work item form group with the height property omitted, using the linked documentation as the expected behavior. Inspect the contribution rendering around the vss-contentHost parent and external-content-iframe, then compare both computed heights with a manifest that sets height explicitly. Done means the documented sizing behavior is consistent at both levels or the discrepancy is clearly documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
css, html, typescript
Domain
frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.