Chrome has been migrating its built-in PDF viewer from GuestView (separate WebContents with an <embed> element) to OOPIF (Out-of-Process Iframe). Chrome 145 appears to be where this became the default.
* Save the new queries when manually sorting the work packages
* fixup! Save the new queries when manually sorting the work packages
* fixup! Save the new queries when manually sorting the work packages
* change some of stylesheets
* change the style naming
* resolve the error
* improving the previous commit with Ben's comments
* improve the styles of breadcrumb
* change the stylesheet related to status button
* refactoring css stylesheets of wp single card
* fixing the errors of PR, correct selector
* change some of stylesheets
* change the style naming
* resolve the error
* improving the previous commit with Ben's comments
* improve the styles of breadcrumb
* change the stylesheet related to status button
* refactoring css stylesheets of wp single card
* fixing the errors of PR, correct selector
* resolve the error on PR related to boards onboarding
* wp relation and list view style changes
* resolve the errors of previous commit
* fix error in selecting wp relation
* fix the errors of wp relations ruby tests
* change the stylesheets of autocompleter and wp calendar
* change the style of grid page
* Some improvements to the BEM styling
* Prefix draggable-autocomplete BEM block with op-
* Fix spec selector
* Fix spec selector
Co-authored-by: Benjamin Bädorf <b.baedorf@openproject.com>
Updates the copyright to 2021 for all files that have a copyright. Files in our source code without the copyright header still do not receive one automatically. Additionally, backlisted files are also excluded.
Previously the copyright of chiliproject which references redmine stated a copyright of redmine up to and including 2017 which is not true for the code we have in here. Because of that I changed that to 2013
* Check edit fields for Work package dependencies
* Make EditForm, NotificationService, EditContext indepenedent of Work Packages
* Make EventsService independent of WorkPackages
* Start renaming WpNotificationService (WiP)
* Fix more references
* Fix typescript errors
* Add basic halEditingService
* Rename to global halResourceEditingService (WiP)
* Move typing from class to methods (WiP)
* Fix typescript errors
* Remove space in type
* Add test project widget && generalize the editFieldGroup
* Rename editing portal service
[ci skip]
* Rename WpEditFieldComponent
* Rename WpDisplayFields
* Rename display-XX-field to XX-display-field
[ci skip]
* Add WP specific ID field to distinguish between resources
* Re-add state in work package resource
* Generalize display field renderer
* Rename spent-time to wp-spent-time and fix highlight specifics
[ci skip]
* Actually load the project schema and make field editable
* Make edit-field-group.component an edit-form.component and subclass EditForm
* Remove edit context in favor of specialized EditForm
* Add special cases for work package editing
* Fix edit actions bar
* Fix codeclimate issues
* Use WorkPackageNotificationService if necessary
* Override NotificationService for WPs to allow WP specififc notifications (WiP)
* Correctly provide wpNotification service
Because the ui-router doesn't seem to correctly use the parent element's
injector, we need to provide the wpNotification service not in the
wp-base, but rather the wp-list component as well as in the isolated
query space.
* Allow to filter halEvents for specific resourceTypes (e.g. WorkPackage)
* Remove superfluous cell class constant
* Start renaming selectors for wp-edit-field into generics
* Remove wp-table--cell-span in favor of display field selector
* Consolidate other display and edit field styles
* Provide specialized service for transitions in active edit forms
* Remove superfluous overflowSelector
* Accept that date field contains some work package specifics
* Ignore unreadable files
* Provide the changeset for work packages as a hook
Since hal resource editing service is provided per query space, we
cannot register them once (would only work globally)
* Fix dangerfile
* Remove another todo in halResourceNotification service
* Fix npm TestBed for changed dependencies
* Show inplace edit field in project details widget
* Fix highlighting in single view
* Provide HalResourceEditingService outside of project context
* Used typedState for single-view
* Also provide wpNotification service in split view
* Correct check for resource type in eventsService
* Fix getSchemaName in display field renderer
* Fix passing ids into `halEditing.stopEditing`
* Do not globally inject the halResourceEditingService
There's a bug(?) in ui-router that gives you the global service before
the parent injected service for a ui-view
* Fix wpCreate service on copying and parallel creation
* Remove test project widget
* Revert changes for project details widget
In case the fixed version and the status of a work package are both closed, the status of a work package cannot be altered any more. Attempting it will result in an error.
Before the fix, the possible status calculation would not factor in that situation and the status would be marked as writable regardless as well. Therefore, the frontend would display a list of statuses even though selecting one would do nothing at all.
Now, the status property is marked as non writable in such a situation and the status list will only contain the current status. As we only fetch the form after a click on the edit field, we can only disable the field after that which is a bit weird.
* Introduce ng-select component on WP pages
* Remove multiselect switch within multiselect component
* Append autocomleter dropdown to attribute group to better handle the two colum layout
* Add overflow selector to edit contexts to allow adding to it
* Set correct element to append to on WP table and WP view
* Make dropdown in Subject row visible and start fixing tests
* Fix tests
* Append wp autocomplete dropdown to body
* Pass user activation requests to edit field
[ci skip]
* Directly open select fields on click
* Include ng-select from own fork
* Add path to tsconfig.json to resolve the module
* Make attributes group id fix, so that it stays the same after reinitialisation (e.g. type change)
[ci skip]
The permission to edit the work package is controlled through the HAL link workPackage.update
For new work packages, add_work_packages permission leads update link of /api/v3/projects/X/work_packages/form
When saving the work package, no update links is returned (correct, since you don't have the permission).
The returning HAL+JSON is merged back into the frontend resource, leaving the old update link, which is now invalid.
https://community.openproject.com/wp/28580
* Add new WP status selector button [WIP]
* Change styling and add little permission handling
* Store changed status
* Adapt new styling
* Show status depending on the changeset
* Remove status button from create form && reduce height of info row
* Adjust test cases, add success message, support for help texts and transfer css variables
[ci skip]
This causes the multivalue change event to fail complete in Chrome.
For consistency, I added the ngModelOptions to clarify use of
getter/setter on the model variable.
https://community.openproject.com/wp/26611
ulferts