# Bug SSI-236 - Pattern input style issues

Project: Stream Storage Integrations
Status: closed
URL: https://community.openproject.org/work_packages/SSI-236

## Open points

_No work packages_

## Details

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Module |  |
| Target versions | 15.4.0 |
| Observed in versions | 15.3.0 |
| Bug found in version (deprecated) | 15.3.x |
| Requires doc change | No |
| Accessibility | No |
| Pull preview |  |
| List |  |
| Labels |  |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable | Eric Schubert |
| Product manager |  |
| Developers |  |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Planning

| Attribute | Value |
| --- | --- |
| Relevance |  |

## Costs

| Attribute | Value |
| --- | --- |
| Votes |  |
| Work |  |
| Labor costs |  |

## Description

### Steps to reproduce

1.  Login as an admin user
    
2.  Make sure to have enterprise enabled
    
3.  Go to administration -&gt; work packages -&gt; types -&gt; any type -&gt; subject configuration tab
    
4.  Click on &quot;Automatically generated subjects&quot;
    
5.  Type in any character to open the suggestions
    

### What is the buggy behavior?

*   The field is taking up the full width of the browser, but [according to the designs](https://www.figma.com/design/I2IVNb97j1fNNCs32H6p2m/Automatic-generated-subjects?node-id=0-1&p=f&t=2DtpPPNwFjOGgF5Z-0) it should take only half
    
    <img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/308460/content">
    
*   Separators are overflowing past the suggestions box
    
    <img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/308459/content">
    

### What is the expected behavior?

_Describe how the application should behave like. Example:_

1.  Width of the field according to design
    
2.  Dividers not overflowing
    

<br>

**Technical notes**

*   Two possible solutions
    
    *   Input width possibility is added to the input and can be defined like for other form fields
        
    *   Do not add possibility of width changes and solve the problem by moving forms into containers. This would also solve the CKEditor width problem.
        
*   Additional input from Primer Design team is needed
